You are in an open bitfield on the west side of a large template class.
In front of you is an enum.
>TAKE ENUM
Taken.
> WEST
You're in a dirty piece of legacy code. An inline function is visible.
>LOOK INTO THE FUNCTION
You see only darkness.
>STEP INTO THE FUNCTION
You are likely to be eaten by a grue. If this predicament seems particularly cruel, consider whose fault it could be. Not a -g or an -O0 in your compile flags.
>S
Opcodes/grue.c:17457: internal compiler error: in vect_get_vec_def_for_operand, at tree-vect-transform.c:1999
Please submit a full bug report,
with preprocessed source if appropriate.
*** You have died ***
Your score is 0 out of a possible 2147483647
Posted May 27, 2012 21:14 UTC (Sun) by speedster1 (subscriber, #8143)
[Link]
Thanks, that was so excellent.
Makes me want -infocom flag in gcc 5!
Would provide bit of consolation for hitting those blasted internal compiler errors, kind of like having screen crash with nethack mode on: "suddenly the dungeon collapses"
GCC Explorer - an interactive take on compilation
Posted May 27, 2012 22:48 UTC (Sun) by SiliconSlick (subscriber, #39955)
[Link]
PLUGH
SS (not sure if that will help at that point)
GCC Explorer - an interactive take on compilation
Posted May 28, 2012 8:57 UTC (Mon) by mpr22 (subscriber, #60784)
[Link]