Thread: Today I crashed gcc!

I just felt like I had to share this because I consider it an achievement! ^_^
Btw, the same code compiles fine with Visual C++ and clang.

g++ -std=c++1y -O -fopenmp -fdump-tree-ompexp -lboost_math_tr1 -I . -o recursive_omp_gcc recursive_omp_solution.cpp -g
In file included from recursive_omp_solution.cpp:7:0:
./Stuff/Statistics.hpp:28:8: internal compiler error: in gen_type_die_with_usage, at dwarf2out.c:19486
class XStatistics
^
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.8/README.Bugs> for instructions.
Preprocessed source stored into /tmp/ccOXYWdn.out file, please attach this to your bugreport.

Interestingly enough, removing the "-g" flag causes the compiler to compile fine (but the program still crashes and I don't know why; it works fine with clang and VC).

For those interested, here's a link to the source of the code that crashed the compiler. It will a nice little note in the history books.

Meh! You consider it an achievement. I'd say you're compounding your lack of achievement by not reporting the bug. Can we expect a rant in a few months about how the gcc maintainers don't fix the problem, despite the fact you haven't reported it?

Tickling a compiler bug when you're using relatively new/developmental/experimental features (which is certainly the case from that command line) is not exactly an achievement. With any compiler.

I've personally lost count of the number of compiler bugs I've reported - including bugs in clang, VC, as well as quite a few ICE reports for gcc. But, when I encounter them, I report them with all details needed, rather than posting in a forum that I'm not going to report the problem.

I like to call this an achievement because it's my first time crashing gcc and I find it funny, so it's an achievement to me, though not necessarily a "real" achievement. This is my first time crashing gcc. I'm not posting this here because I want someone else to report a problem or to complain about something. I posted it because I found it funny.

I'm not going to rant about things not getting fixed. I don't do that. I don't make posts on forums about things that don't work while providing "no details," because I find that to be a pointless post. And I certainly can't be bothered to report it due to the work in takes in read up how to submit it, where to submit it, subscribe to mailing list, etc. Takes too much time and I get too little gain from it. I know full well it's not going to get fixed then, but I'm not going to complain or rant about it.

No, I don't expect anyone to do my "legwork." I shared something I found funny.

EDIT:
Removed the "bug report" part, so one thinks I want someone else to do it for me >_<
Really, I don't. Please don't submit it on my behalf.

Well ..... thanks for the insight into your sense of humour.

It explains more than you realise.

Well... you know, when working on a huge project with a deadline approaching, running into an internal compile error might not very fun.
But when poking around with testing code and compilers and stuff for fun, crashing the compiler can be a fun thing.
I certainly found it more humorous than annoying this time around.

I'm not going to rant about things not getting fixed. I don't do that. I don't make posts on forums about things that don't work while providing "no details," because I find that to be a pointless post. And I certainly can't be bothered to report it due to the work in takes in read up how to submit it, where to submit it, subscribe to mailing list, etc. Takes too much time and I get too little gain from it. I know full well it's not going to get fixed then, but I'm not going to complain or rant about it.

O_o

Looks like a duck...

Soma

Report it, mang!!!

O_o

I appreciate that you and grumpy weren't having the problem, but the problem here is pretty much just Elysia... being Elysia.

[Edit]
I wonder to whom you'd report that bug? ^_^;
[/Edit]

Despite all the times Elysia has barked at someone to use a different compiler or upgrade their compiler, Elysia is using an older version.

The first thing to do is actually see if the current compiler works before even considering a bug report.

Soma

Originally Posted by phantomotap

Despite all the times Elysia has barked at someone to use a different compiler or upgrade their compiler, Elysia is using an older version.

I use an older version here because of the same reason I stick to an older version in Windows... the reason being that some lazy package maintainer has failed to update the package to the latest version in the linux repository. It's not my main compiler, so I don't want to bother trying to manually compile gcc to get the latest version. VC is different. Just download latest version, install, done. Not so with gcc/clang.

the reason being that some lazy package maintainer has failed to update the package to the latest version in the linux repository.

O_o

Okay. I'll bite. What distribution and/or package manager are you using?

Soma

Is this not the latest version of gcc?

O_o

Your compiler is irrelevant unless you are going to try to reproduce the error.

I was making you aware that Elysia is not using the latest version.

You said "Report it, mang!!!", but the occurrence should not be reported until reproduced on the latest version as the problem may have already been fixed.

Soma