This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: How to deal with unrecognizable RTL code

From: Jim Wilson <wilson at codesourcery dot com>
To: "daniel.tian" <daniel dot tian at mavrixtech dot com dot cn>
Cc: 'Jeff Law' <law at redhat dot com>, gcc at gcc dot gnu dot org, 'Peng Zheng' <peng dot zheng at mavrixtech dot com>, thomas dot liau at mavrixtech dot com
Date: Mon, 29 Jun 2009 19:07:54 -0700
Subject: Re: How to deal with unrecognizable RTL code
References: <4A43C3F9.4080508@redhat.com> <20090629095144.9C9D13758001@mail.mavrixtech.com.cn>

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

References:
- Re: How to deal with unrecognizable RTL code
  - From: Jeff Law
- Re:How to deal with unrecognizable RTL code
  - From: daniel.tian

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]