From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <glibc-bugs-return-24018-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Received: (qmail 17552 invoked by alias); 23 Jun 2014 20:10:03 -0000
Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <glibc-bugs.sourceware.org>
List-Subscribe: <mailto:glibc-bugs-subscribe@sourceware.org>
List-Post: <mailto:glibc-bugs@sourceware.org>
List-Help: <mailto:glibc-bugs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: glibc-bugs-owner@sourceware.org
Received: (qmail 17491 invoked by uid 55); 23 Jun 2014 20:09:58 -0000
From: "joseph at codesourcery dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/17082] htons et al.: statement-expressions prevent use on global scope with -O1 and higher
Date: Mon, 23 Jun 2014 20:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: libc
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: joseph at codesourcery dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-17082-131-yLJq8ShOPk@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-17082-131@http.sourceware.org/bugzilla/>
References: <bug-17082-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-06/txt/msg01394.txt.bz2

https://sourceware.org/bugzilla/show_bug.cgi?id=17082

--- Comment #1 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
Policy questions should best be taken to libc-alpha (by someone willing to 
take the lead in getting the discussion to consensus and then documenting 
the resulting consensus on the wiki, not just posting a one-off question 
and waiting for an answer to emerge) rather than filed as bugs; Bugzilla 
is best for something where the presence of a defect is unambiguous under 
existing policy.  If such a consensus were in the direction you propose, 
any bugs filed should be separate bugs for each function or header 
involved so it is clear what is or is not fixed rather than needing to 
track some bugs as partly fixed.

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