https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63155
Bug ID: 63155
Summary: [4.9/5 Regression] memory hog
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: doko at gcc dot gnu.org
Created attachment 33441
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33441&action=edit
preprocessed source
[forwarded from https://bugs.debian.org/759683]
compiling the attached test case with the 4.9 branch r214759 and trunk r213954
takes about 90sec on x86_64 and 10GB of memory. succeeds with the 4.8 branch in
less than a second.
$ gcc -std=c99 -c testunity_Runner.i
from the Debian issue:
"""
Notice that replacing "_setjmp
(Unity.AbortFrame[Unity.CurrentAbortFrame])" in main function by
"_setjmp (Unity.AbortFrame[0])", make gcc works normaly.
After few tests it seems that gcc does not like having a variable in here.
"""
I don't see the crash reported in the Debian issue.
