From: Ian Lance Taylor <iant@google.com>
To: Kenneth Zadeck <zadeck@naturalbridge.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>, "Bonzini\,
Paolo" <bonzini@gnu.org>,
Richard Sandiford <rsandifo@nildram.co.uk>
Subject: Re: [trunk] Addition to subreg section of rtl.text.
Date: Fri, 14 Mar 2008 14:51:00 -0000 [thread overview]
Message-ID: <m3skytqs25.fsf@google.com> (raw)
In-Reply-To: <47DA8A3E.7060002@naturalbridge.com> (Kenneth Zadeck's message of "Fri\, 14 Mar 2008 10\:22\:54 -0400")
Kenneth Zadeck <zadeck@naturalbridge.com> writes:
> Does every one agree that what i am adding is correct?
It looks right to me.
Ian
prev parent reply other threads:[~2008-03-14 14:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-14 14:24 Kenneth Zadeck
2008-03-14 14:45 ` Richard Sandiford
2008-03-14 14:48 ` Ian Lance Taylor
2008-03-14 14:49 ` Kenneth Zadeck
2008-03-14 14:51 ` Ian Lance Taylor
2008-03-14 14:59 ` Kenneth Zadeck
2008-03-14 15:17 ` Richard Sandiford
2008-03-14 17:00 ` Kenneth Zadeck
2008-03-14 17:14 ` Richard Sandiford
2008-03-14 14:51 ` 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=m3skytqs25.fsf@google.com \
--to=iant@google.com \
--cc=bonzini@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=rsandifo@nildram.co.uk \
--cc=zadeck@naturalbridge.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).