From owner-freebsd-numerics@freebsd.org  Wed Sep 13 09:47:39 2017
Return-Path: <owner-freebsd-numerics@freebsd.org>
Delivered-To: freebsd-numerics@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5E9AFE17526
 for <freebsd-numerics@mailman.ysv.freebsd.org>;
 Wed, 13 Sep 2017 09:47:39 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 4C7F1800BE
 for <freebsd-numerics@FreeBSD.org>; Wed, 13 Sep 2017 09:47:39 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v8D9lbk8095732
 for <freebsd-numerics@FreeBSD.org>; Wed, 13 Sep 2017 09:47:39 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-numerics@FreeBSD.org
Subject: [Bug 222247] libmsun tests does not compile during a buildworld
Date: Wed, 13 Sep 2017 09:47:38 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: bin
X-Bugzilla-Version: 11.1-STABLE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: kib@FreeBSD.org
X-Bugzilla-Status: In Progress
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: rlibby@freebsd.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-222247-18636-mtQ4P18dJr@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-222247-18636@https.bugs.freebsd.org/bugzilla/>
References: <bug-222247-18636@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-numerics@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: "Discussions of high quality implementation of libm functions."
 <freebsd-numerics.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-numerics>, 
 <mailto:freebsd-numerics-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-numerics/>
List-Post: <mailto:freebsd-numerics@freebsd.org>
List-Help: <mailto:freebsd-numerics-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-numerics>, 
 <mailto:freebsd-numerics-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Sep 2017 09:47:39 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222247

Konstantin Belousov <kib@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kib@FreeBSD.org

--- Comment #7 from Konstantin Belousov <kib@FreeBSD.org> ---
(In reply to Ryan Libby from comment #6)
First, we are the implementation.  So at least in the hosted case, we are
allowed to introduce the __* and _[A_Z] symbols.

Second, defining something in userspace and then undefining it at the end of
the file still breaks user namespaces.  Consider what would happen if user
defines an allowed symbol and then includes such file.

Also, note that the restrictions on the user namespace pollution are only
applicable to the standard-specified files.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=