From: "Richard Guenther" <richard.guenther@gmail.com>
To: tromey@redhat.com
Cc: "Diego Novillo" <dnovillo@google.com>,
"Gcc Patch List" <gcc-patches@gcc.gnu.org>
Subject: Re: [incremental] Patch: FYI: delay gimplification + partial cgraph revert
Date: Sat, 29 Sep 2007 21:30:00 -0000 [thread overview]
Message-ID: <84fc9c000709291051l1bd771c0vca592745b764ace0@mail.gmail.com> (raw)
In-Reply-To: <m3d4w1pf44.fsf@fleche.redhat.com>
On 9/29/07, Tom Tromey <tromey@redhat.com> wrote:
> >>>>> "Diego" == Diego Novillo <dnovillo@google.com> writes:
>
> Diego> On 9/28/07, Tom Tromey <tromey@redhat.com> wrote:
> >> Though the current patch is flawed, I think this is a good direction
> >> for the compiler to go.
>
> Diego> I agree. Would you consider moving this into mainline when stage1
> Diego> opens again? Delaying gimplification on the C/C++ FEs is a Good
> Diego> Thing.
>
> Sure thing. Though perhaps Michael will beat me to it :-)
There were concerns about memory usage regressions (it's not clear
whether the un-gimplified or the gimplified variant takes more memory).
Richard.
next prev parent reply other threads:[~2007-09-29 17:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-29 4:11 Tom Tromey
2007-09-29 17:51 ` Diego Novillo
2007-09-29 19:26 ` Tom Tromey
2007-09-29 21:30 ` Richard Guenther [this message]
2007-09-30 11:17 ` Tom Tromey
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=84fc9c000709291051l1bd771c0vca592745b764ace0@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=dnovillo@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=tromey@redhat.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).