From: Ian Lance Taylor <iant@google.com>
To: John Marino <gnugcc@marino.st>
Cc: gcc-help@gcc.gnu.org
Subject: Re: dl_iterate_phdr support
Date: Mon, 14 Feb 2011 17:46:00 -0000 [thread overview]
Message-ID: <mcrd3mubjfr.fsf@google.com> (raw)
In-Reply-To: <4D58E3BB.10002@marino.st> (John Marino's message of "Mon, 14 Feb 2011 09:11:39 +0100")
John Marino <gnugcc@marino.st> writes:
> Thanks Ian. If I understand the code in those two files correctly,
> only Solaris, Linux, and FreeBSD is being considered. If I want to
> use this on Dragonfly 2.9+, NetBSD 5.99+, and/or OpenBSD, I'll have to
> patch these files will the appropriate code.
Right, or even better generalize the test somehow.
> For the others, I am waiting for gcc 4.6 to get branched. Would a
> configuration patch to these files make it into trunk before it's
> branched? If you take the words "regression fixes and documentation
> only" literally then the answer would be no, it has to wait for 4.7
> stage 1.
Generally target specific patches get additional leeway even in stage 4.
That would be a question for the *BSD maintainers.
Ian
prev parent reply other threads:[~2011-02-14 17:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-13 2:15 John Marino
2011-02-14 8:11 ` Ian Lance Taylor
2011-02-14 15:48 ` John Marino
2011-02-14 17:46 ` Ian Lance Taylor [this message]
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=mcrd3mubjfr.fsf@google.com \
--to=iant@google.com \
--cc=gcc-help@gcc.gnu.org \
--cc=gnugcc@marino.st \
/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).