From: dewar@gnat.com (Robert Dewar)
To: aph@redhat.com, gyana_m@hotmail.com
Cc: gcc@gcc.gnu.org
Subject: Re: Dumping RTL???
Date: Tue, 03 Dec 2002 07:37:00 -0000 [thread overview]
Message-ID: <20021203125254.2EC95F2E22@nile.gnat.com> (raw)
I must say I still don't understand the motivation behind the split
in this particular case. Splitting gcc into two parts has no particular
benefit of its own.
next reply other threads:[~2002-12-03 15:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-03 7:37 Robert Dewar [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-08 18:55 Robert Dewar
2002-12-08 11:59 Richard Kenner
2002-12-08 8:16 Richard Kenner
2002-12-08 10:36 ` Daniel Berlin
2002-12-08 7:49 Richard Kenner
2002-12-08 7:25 Robert Dewar
2002-12-08 7:24 Robert Dewar
2002-12-05 1:07 Barak Zalstein
2002-12-04 21:18 Robert Dewar
2002-12-04 19:22 Richard Kenner
2002-12-08 7:23 ` Marc Espie
2002-12-04 15:57 Chris Lattner
2002-12-02 21:52 Chris Lattner
2002-12-02 20:39 gyanindra mishra
2002-12-03 3:00 ` Andrew Haley
2002-12-03 4:13 ` Fabio Alemagna
2002-12-03 11:36 ` Joe Buck
2002-12-04 15:13 ` Svein E. Seldal
2002-12-08 7:17 ` Marc Espie
2002-12-02 6:57 Robert Dewar
2002-12-02 6:01 gyanindra mishra
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=20021203125254.2EC95F2E22@nile.gnat.com \
--to=dewar@gnat.com \
--cc=aph@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gyana_m@hotmail.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).