From: Mike Stump <mikestump@comcast.net>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"echristo@apple.com" <echristo@apple.com>,
"stanshebs@earthlink.net" <stanshebs@earthlink.net>
Subject: Re: Put libgcc config headers in separate libgcc_tm.h
Date: Tue, 10 May 2011 17:50:00 -0000 [thread overview]
Message-ID: <56997387-85D9-4E9D-871E-E4C62EAA61F7@comcast.net> (raw)
In-Reply-To: <Pine.LNX.4.64.1105101525350.6103@digraph.polyomino.org.uk>
On May 10, 2011, at 8:26 AM, "Joseph S. Myers" <joseph@codesourcery.com> wrote:
> On rerunning my target macro enumeration now it's no longer necessary
> to consider libgcc/config/ macros in host-side files
> OK to commit?
Ok.
>
prev parent reply other threads:[~2011-05-10 16:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-07 20:37 Joseph S. Myers
2011-05-10 14:16 ` Ian Lance Taylor
2011-05-10 15:43 ` Joseph S. Myers
2011-05-10 17:50 ` Mike Stump [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=56997387-85D9-4E9D-871E-E4C62EAA61F7@comcast.net \
--to=mikestump@comcast.net \
--cc=echristo@apple.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=stanshebs@earthlink.net \
/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).