From: Jim Wilson <wilson@redhat.com>
To: "Avinash K. Shrivastava" <avi@cse.iitb.ac.in>
Cc: gcc@gcc.gnu.org
Subject: Re: reading the gcc-IR in back-end
Date: Wed, 16 Oct 2002 11:42:00 -0000 [thread overview]
Message-ID: <xwuk7kip9e8.fsf@tonopah.toronto.redhat.com> (raw)
In-Reply-To: <Pine.HPX.4.21.0210131437350.12122-100000@everest.cse.iitb.ac.in>
>[2] Do we need to modify it [back-end] to read the IR from a file instead
> of from the memory.
If you do that, we won't be able to accept the patch into gcc.
Jim
next prev parent reply other threads:[~2002-10-16 17:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-13 7:39 Avinash K. Shrivastava
2002-10-13 13:45 ` Pop Sébastian
2002-10-16 11:42 ` Jim Wilson [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-13 7:06 Avinash K. Shrivastava
2002-10-13 11:19 ` Avinash K. Shrivastava
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=xwuk7kip9e8.fsf@tonopah.toronto.redhat.com \
--to=wilson@redhat.com \
--cc=avi@cse.iitb.ac.in \
--cc=gcc@gcc.gnu.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).