This is the mail archive of the
mailing list for the GCC project.
Re: Fwd: [PATCH] Fix may_alias canonical types regression
- From: Mark Mitchell <mark at codesourcery dot com>
- To: Doug Gregor <doug dot gregor at gmail dot com>
- Cc: Gcc Patch List <gcc-patches at gcc dot gnu dot org>
- Date: Sat, 11 Oct 2008 14:47:39 -0700
- Subject: Re: Fwd: [PATCH] Fix may_alias canonical types regression
- References: <email@example.com> <firstname.lastname@example.org> <48DD7B11.email@example.com> <firstname.lastname@example.org> <48DFC628.email@example.com> <firstname.lastname@example.org> <48EA3C2E.email@example.com> <firstname.lastname@example.org>
Doug Gregor wrote:
> On Mon, Oct 6, 2008 at 12:26 PM, Mark Mitchell <email@example.com> wrote:
>> This seems sensible. However, I think it would be useful to measure the
>> memory footprint of GCC with this change on some big C++ code.
>> (libstdc++ or Boost++ or some such). DECLs are big, and if we have a
>> whole lot more of them, we might be unhappy, and want to look for
>> another way to solve this. So, would you please measure and report?
> It's _TYPE nodes we'd be duplicating with this. I did a quick check
> with a reasonably large testcase from the Boost Graph Library (194k
> lines of preprocessed code, lots of system headers, templates,
> template instantiations, etc.).
I'm comforted. The patch is OK.
(650) 331-3385 x713