This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Addressing Mode Woes
The way you debug a problem like this is to
cd yourbuildtree/gcc
gdb ./cc1
run testcase.c
and when you get the abort(), you can do a stack trace to see
where you are and typically what's wrong with your RTL. There's a
.gdbinit file created in the build directory that sets a breakpoint on the fancy_abort
or somewhere similar so that you can just do a
where
and see everything revealed....
Good luck!
Al Lehotsky
p.s. The other useful thing you should know is that setting a conditional breakpoint in make_insn_raw()
is very useful when you have an INSN that appears to be corrupt when it's created. [E.g., the first
RTL dump that the insn appears in, it already looks wrong] Also be aware that cur_insn_uid is a macro!
--
------------------------------------------------------------------------
Quality Software Management
http://home.earthlink.net/users/~qsmgmt
apl@alum.mit.edu
(978)287-0435 Voice
(978)808-6836 Cell
(978)287-0436 Fax
Software Process Improvement and Management Consulting
Language Design and Compiler Implementation