This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/54332] [4.8 Regression] 481.wrf in SPEC CPU 2006 takes > 10GB memory to compile
- From: "dnovillo at google dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 21 Aug 2012 20:49:16 +0000
- Subject: [Bug fortran/54332] [4.8 Regression] 481.wrf in SPEC CPU 2006 takes > 10GB memory to compile
- Auto-submitted: auto-generated
- References: <bug-54332-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54332
--- Comment #25 from dnovillo at google dot com <dnovillo at google dot com> 2012-08-21 20:49:16 UTC ---
On 2012-08-21 15:53 , hjl.tools at gmail dot com wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54332
>
> --- Comment #24 from H.J. Lu <hjl.tools at gmail dot com> 2012-08-21 19:53:14 UTC ---
> (In reply to comment #23)
>>
>> The problem with this is that you are switching a stack vec into a heap
>> vec. This may not always be what the caller wanted.
>
> My patch just restores the old behavior.
You are right. This was always the case. I added the extra check to
guard against inadvertent *initial* heap allocations for stack vectors.
But now that I see the old code, this was always the case. The
subsequent stack operations after the first round around the loop will
move the stacks into the heap.
The patch is OK with a ChangeLog and bootstrap testing.
Thanks! Diego.