From: Cary Coutant <ccoutant@google.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Joern Rennecke <amylaar@spamcop.net>,
"Ansari, Zia" <zia.ansari@intel.com>,
GCC Development <gcc@gcc.gnu.org>,
GNU C Library <libc-alpha@sourceware.org>,
Binutils <binutils@sourceware.org>
Subject: Re: RFC: Add STB_GNU_SECONDARY
Date: Fri, 20 Apr 2012 22:11:00 -0000 [thread overview]
Message-ID: <CAHACq4qr7tuhLAD6vwNFh8W_ib3HYa6ynppJiyd4r=zaETWvXQ@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOpNqs933DZejuBV4tjcyLnc29Z3302vkj5LN1Y23Pnzmg@mail.gmail.com>
> We only have very few bits to in STB_XXX field.
This is exactly why I'm not in favor of this extension. The feature
doesn't seem compelling enough to use up one of these precious
reserved values (in fact, you're using the next-to-last one that's
reserved for OS use).
You want a backup definition? Put a weak def at the end of the link line.
-cary
next prev parent reply other threads:[~2012-04-20 22:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 19:47 H.J. Lu
2012-04-20 19:51 ` Roland McGrath
2012-04-20 20:11 ` H.J. Lu
2012-04-20 20:27 ` Roland McGrath
2012-04-20 20:36 ` H.J. Lu
2012-04-20 22:55 ` Petr Baudis
2012-04-20 23:30 ` H.J. Lu
2012-04-20 20:56 ` Joern Rennecke
2012-04-20 21:20 ` H.J. Lu
2012-04-20 22:11 ` Cary Coutant [this message]
2012-04-20 22:48 ` H.J. Lu
2012-04-20 22:49 ` H.J. Lu
2012-04-20 22:59 ` Ian Lance Taylor
2012-04-20 23:36 ` H.J. Lu
2012-04-20 23:40 ` Ian Lance Taylor
2012-04-20 23:51 ` H.J. Lu
2012-04-21 0:49 ` Ian Lance Taylor
2012-04-21 1:04 ` H.J. Lu
2012-04-21 1:07 ` Ian Lance Taylor
2012-04-21 1:09 ` Joern Rennecke
2012-04-21 13:53 ` H.J. Lu
2012-04-21 19:01 ` Joern Rennecke
2012-04-23 18:12 ` H.J. Lu
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='CAHACq4qr7tuhLAD6vwNFh8W_ib3HYa6ynppJiyd4r=zaETWvXQ@mail.gmail.com' \
--to=ccoutant@google.com \
--cc=amylaar@spamcop.net \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=zia.ansari@intel.com \
/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).