daniel.tian wrote:
Hi,
I check the MIPS and ARM, both those cc1 files opened in Insight debug tool
contain the mips.md and arm.md file. It is convenient while break point can
be set in it.
My port md file doesn't appear in the insight.
The mips.md and arm.md file end up in the debug info because they
contain C code segments that get copied into the insn-*.c files. If you
look at these insn-*.c files, you will see things like (copied from i386
port)
#line 1310 "../../gcc/gcc/config/i386/i386.md"
which causes debug info to be generated that includes a reference to
this file.
If you have a very simple port, you might not have any such cases like
this. Without this debug info, Insight (aka gdbtk) won't be able to
show the files.
Or something could be broken in your port.
Jim
