public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <bug-17082-131-yLJq8ShOPk@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17082-131@http.sourceware.org/bugzilla/>

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.


  reply	other threads:[~2014-06-23 20:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-23 19:53 [Bug libc/17082] New: " jh_sourceware.org at sotun dot de
2014-06-23 20:10 ` joseph at codesourcery dot com [this message]
2014-06-24  7:40 ` [Bug libc/17082] " fweimer at redhat dot com
2015-03-15  7:59 ` cemkalyoncu at gmail dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-17082-131-yLJq8ShOPk@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).