http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47311
--- Comment #5 from Pawel Sikora <pluto at agmk dot net> 2011-01-15 23:20:41
UTC ---
(In reply to comment #2)
> (In reply to comment #1)
> > (In reply to comment #0)
> > > current gcc-trunk (r168844) ICEs on my codebase:
> > >
> > > accidentally, the --save-temps (or -std=gnu++98) removes the ICE,
> > > so how can i produce a preprocessed source for full bug report?
> >
> > -E and -S.
> >
>
> Also use valgrind.
==28506==
==28507== Memcheck, a memory error detector
==28507== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al.
==28507== Using Valgrind-3.6.0 and LibVEX; rerun with -h for copyright info
==28507== Command:
/local/devel/toolchain46/x86_64-gnu-linux.host64/lib64/gcc/x86_64-gnu-linux/4.6.0/cc1plus
-E -quiet -I ./h -I ./factories -I ./utils -I ../VCM/h -I ../def/h -I
../hescore/h -I ../debugtools/h -I ../au/h -I ../dp/h -D_GNU_SOURCE
-D_REENTRANT -D HDL_EXPORTS -D _GNU_SOURCE -D _GLIBCXX_DEBUG -D _DEBUG -D
BOOST_EXCEPTION_DISABLE -isystem
../../buildenv/linux/gcc-4.6/64/boost-1.44.0/include hdlVhdlArchitecture.cpp
-mcld -march=x86-64 -std=gnu++0x -Wall -Wno-uninitialized -Wno-deprecated
-Wsign-compare -Wtype-limits -Woverloaded-virtual -Werror -fdwarf2-cfi-asm
-feliminate-unused-debug-types -fno-strict-aliasing -fno-schedule-insns
-fno-schedule-insns2 -fPIC -gdwarf-4 -g2 -fworking-directory -O1 -O2
==28507==
parse_type_DIE: confused by:
<1><1444a3e>: DW_TAG_array_type
DW_AT_type : 8 byte signature: 36 56 52 8f ec 5e fc e3
DW_AT_sibling : <1444a52>
--28507-- WARNING: Serious error when reading debug info
--28507-- When reading debug info from
/local/devel/toolchain46/x86_64-gnu-linux.host64/lib64/gcc/x86_64-gnu-linux/4.6.0/cc1plus:
--28507-- parse_type_DIE: confused by the above DIE
vex amd64->IR: unhandled instruction bytes: 0x66 0xF 0x3A 0x61 0x7 0x0
==28507== valgrind: Unrecognised instruction at address 0xb43594.
==28507== Your program just tried to execute an instruction that Valgrind
==28507== did not recognise. There are two possible reasons for this.
==28507== 1. Your program has a bug and erroneously jumped to a non-code
==28507== location. If you are running Memcheck and you just saw a
==28507== warning about a bad jump, it's probably your program's fault.
==28507== 2. The instruction is legitimate but Valgrind doesn't handle it,
==28507== i.e. it's Valgrind's fault. If you think this is the case or
==28507== you are not sure, please let us know and we'll try to fix it.
==28507== Either way, Valgrind will now raise a SIGILL signal which will
==28507== probably kill your program.
hdlVhdlArchitecture.cpp:1:0: internal compiler error: Illegal instruction
