[Bug c++/49351] Internal error: Segmentation fault (program cc1plus)

2018-10-17 Thread mpolacek at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49351 Marek Polacek changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC|

[Bug c++/49351] Internal error: Segmentation fault (program cc1plus)

2011-06-10 Thread michael at jarvis dot net
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49351 Mike Jarvis changed: What|Removed |Added Severity|normal |minor --- Comment #10 from Mike Jarvis 201

[Bug c++/49351] Internal error: Segmentation fault (program cc1plus)

2011-06-10 Thread michael at jarvis dot net
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49351 --- Comment #9 from Mike Jarvis 2011-06-10 21:47:37 UTC --- That worked. So I guess g++ is exceeding the stack limit and crashing, not the heap memory. $ ulimit -aH core file size (blocks, -c) 0 data seg size (kbytes, -d) unl

[Bug c++/49351] Internal error: Segmentation fault (program cc1plus)

2011-06-10 Thread michael at jarvis dot net
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49351 --- Comment #8 from Mike Jarvis 2011-06-10 21:26:59 UTC --- $ ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited file size (blocks, -f) unlimited max locked memory (kbytes, -l) unli

[Bug c++/49351] Internal error: Segmentation fault (program cc1plus)

2011-06-10 Thread redi at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49351 --- Comment #7 from Jonathan Wakely 2011-06-10 21:10:16 UTC --- does 'ulimit -a' show any limit on memory size? obviously it would be good if gcc didn't use so much memory, but I did verify that given a sufficiently beefy machine (64-bit, 24GB R

[Bug c++/49351] Internal error: Segmentation fault (program cc1plus)

2011-06-10 Thread michael at jarvis dot net
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49351 --- Comment #6 from Mike Jarvis 2011-06-10 21:04:59 UTC --- I figured out how to install a 64 bit version of g++ on my machine, and I also booted up the machine with 6 and 4 held down to get the 64 bit kernel. And this didn't help. I'm still

[Bug c++/49351] Internal error: Segmentation fault (program cc1plus)

2011-06-10 Thread redi at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49351 --- Comment #5 from Jonathan Wakely 2011-06-10 14:06:19 UTC --- a single 32-bit process won't be able to use that much

[Bug c++/49351] Internal error: Segmentation fault (program cc1plus)

2011-06-10 Thread michael at jarvis dot net
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49351 --- Comment #4 from Mike Jarvis 2011-06-10 14:02:45 UTC --- That's a bit odd. The final function in the .ii file consists of two function calls. If I delete either one of these, the compile succeeds and only uses about 1100M (RSIZE in top).

[Bug c++/49351] Internal error: Segmentation fault (program cc1plus)

2011-06-10 Thread redi at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49351 --- Comment #3 from Jonathan Wakely 2011-06-10 10:39:58 UTC --- "you're gonna need a bigger boat" compiles ok on a 64-bit box, physical memory usage nears 4GB

[Bug c++/49351] Internal error: Segmentation fault (program cc1plus)

2011-06-10 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49351 --- Comment #2 from Richard Guenther 2011-06-10 10:00:58 UTC --- Needs quite some more memory for me ... (doesn't fit in my 3GB box).

[Bug c++/49351] Internal error: Segmentation fault (program cc1plus)

2011-06-09 Thread michael at jarvis dot net
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49351 --- Comment #1 from Mike Jarvis 2011-06-10 00:54:35 UTC --- I should add that g++ version 4.4.4 also fails to work with this code. It gives the same "Internal error: Segmentation fault" that 4.5.2 gave. But g++ 4.0.1 and 4.2.1 do work. Well,