https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86422
--- Comment #8 from Boris Staletic ---
> ulimit -s unlimited
After running that command and enabling swap, for a total of 16GB available
memory, until about 5 minute mark, cc1plus was consuming >4GB. After about five
minute mark, cc1plus
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86422
Richard Biener changed:
What|Removed |Added
Status|NEW |WAITING
--- Comment #7 from Richard
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86422
--- Comment #6 from Richard Biener ---
So with a debug build I can see
(gdb) run
Starting program: /home/abuild/rguenther/gcc8-g/gcc/cc1plus -quiet
/tmp/CodePoint.ii
Program received signal SIGSEGV, Segmentation fault.
0x01576cf6 in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86422
--- Comment #5 from rguenther at suse dot de ---
On July 6, 2018 6:10:23 PM GMT+02:00, "boris.staletic at gmail dot com"
wrote:
>https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86422
>
>--- Comment #4 from Boris Staletic
>---
>I get the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86422
--- Comment #4 from Boris Staletic ---
I get the segmentations fault when running cc1plus directly. No matter if I
pass -quiet or not.
So what's the next step?
Also, I have just noticed "Known to work: 8.1.1". Is that a mistake?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86422
Richard Biener changed:
What|Removed |Added
Keywords||compile-time-hog,
|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86422
--- Comment #2 from Boris Staletic ---
> so this time it's not parsing but code-generation that blows up things.
That makes sense, when I was playing with the file, it took between 5 to 10
seconds to report syntax errors.
Another thing that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86422
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
