From: Richard Guenther <richard.guenther@gmail.com>
To: Jeff Law <law@redhat.com>
Cc: Laurynas Biveinis <laurynas.biveinis@gmail.com>,
Steven Bosscher <stevenb.gcc@gmail.com>,
gcc-patches@gcc.gnu.org
Subject: Re: [gc-improv] Permanent vs function RTL obstack fix
Date: Fri, 08 Apr 2011 14:39:00 -0000 [thread overview]
Message-ID: <BANLkTik7n+Yo2BGDWBXy0TMc+W0ZxuzGzw@mail.gmail.com> (raw)
In-Reply-To: <4D9F1D63.9010509@redhat.com>
On Fri, Apr 8, 2011 at 4:36 PM, Jeff Law <law@redhat.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 04/08/11 07:21, Laurynas Biveinis wrote:
>> 2011/4/8 Steven Bosscher <stevenb.gcc@gmail.com>:
>>>> * stmt.c (label_rtx): Allocate RTX in permanent RTL memory.
>>>
>>> That looks strange, labels should be function specific, except
>>> non-local labels. Maybe you can get away with allocating DECL_NONLOCAL
>>> labels on the permanent rtl obstack?
>>
>> That's a good idea, I will try it once things are stable on the branch.
>>
>>> Perhaps a third, per-translation-unit obstack is necessary?
>>
>> Perhaps. After I finish with permanent rtl obstack, I will measure how
>> large it gets and if it's worthwhile to split out
>> per-translation-obstack out of it.
> And then you'll want a per-statement obstack, then per-expression
> obstack, and before you know it, GCC looks much like it did 20 years ago.
>
> Sigh.
I remember it was fast at that time though ;)
Richard.
next prev parent reply other threads:[~2011-04-08 14:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 6:17 Laurynas Biveinis
2011-04-07 21:33 ` Steven Bosscher
2011-04-08 13:22 ` Laurynas Biveinis
2011-04-08 14:36 ` Jeff Law
2011-04-08 14:39 ` Richard Guenther [this message]
2011-04-08 14:42 ` Jeff Law
2011-04-09 10:34 ` Steven Bosscher
2011-04-10 18:27 ` Laurynas Biveinis
2011-04-10 18:49 ` Basile Starynkevitch
2011-04-11 20:03 ` Jeff Law
2011-04-12 0:22 ` Mike Stump
2011-04-12 2:54 ` Jeff Law
2011-04-12 6:34 ` Steven Bosscher
2011-04-12 7:01 ` Jakub Jelinek
2011-04-12 8:45 ` Steven Bosscher
2011-04-12 10:44 ` Mike Stump
2011-04-12 10:49 ` Steven Bosscher
2011-04-12 15:02 ` Jeff Law
2011-04-12 11:56 ` Bernd Schmidt
2011-04-12 15:31 ` Jeff Law
2011-04-10 18:23 ` Laurynas Biveinis
2011-04-10 22:33 ` Steven Bosscher
2011-04-11 20:08 ` Jeff Law
2011-04-12 11:43 ` Laurynas Biveinis
2011-04-12 11:46 ` Laurynas Biveinis
2011-04-12 17:25 ` Mike Stump
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=BANLkTik7n+Yo2BGDWBXy0TMc+W0ZxuzGzw@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=laurynas.biveinis@gmail.com \
--cc=law@redhat.com \
--cc=stevenb.gcc@gmail.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).