http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49756
Jason Merrill changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49756
--- Comment #8 from Jakub Jelinek 2011-07-22
09:21:52 UTC ---
Author: jakub
Date: Fri Jul 22 09:21:49 2011
New Revision: 176622
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=176622
Log:
PR c++/49756
* libiberty.h (stack_limit_inc
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49756
--- Comment #7 from Jakub Jelinek 2011-07-22
08:33:42 UTC ---
Author: jakub
Date: Fri Jul 22 08:33:37 2011
New Revision: 176617
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=176617
Log:
PR c++/49756
* libiberty.h (stack_limit_inc
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49756
--- Comment #6 from Jason Merrill 2011-07-18
19:34:08 UTC ---
Created attachment 24789
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=24789
my patch
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49756
--- Comment #5 from Jakub Jelinek 2011-07-18
19:30:03 UTC ---
Created attachment 24788
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=24788
gcc47-pr49756.patch
Untested patch. Clueless people will be still able to construct twice or 4
time
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49756
--- Comment #4 from Jason Merrill 2011-07-18
15:22:11 UTC ---
For this testcase, even 30MB isn't enough, but 40MiB is, so I think I'll round
up to 64MB.
I think it's probably best to raise the limit in both places to avoid confusion
when invokin
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49756
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #3 f
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49756
Jason Merrill changed:
What|Removed |Added
Status|NEW |ASSIGNED
AssignedTo|unassigned at
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49756
Richard Guenther changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|