From: Ian Lance Taylor <iant@google.com>
To: "daniel.tian" <daniel.tian@mavrixtech.com.cn>
Cc: "'Jeff Law'" <law@redhat.com>, <gcc@gcc.gnu.org>,
"'Peng Zheng'" <peng.zheng@mavrixtech.com>,
<thomas.liau@mavrixtech.com>
Subject: Re: How to deal with unrecognizable RTL code
Date: Mon, 29 Jun 2009 21:11:00 -0000 [thread overview]
Message-ID: <m37hyu3g6c.fsf@google.com> (raw)
In-Reply-To: <20090629095144.9C9D13758001@mail.mavrixtech.com.cn> (daniel tian's message of "Mon\, 29 Jun 2009 17\:54\:05 +0800")
"daniel.tian" <daniel.tian@mavrixtech.com.cn> writes:
> 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.
You seem to be asking a question about Insight rather than about gcc. I
haven't used Insight in a long time, but when I use gdb it knows about
the .md file (e.g., "list CPU.md:1" works). So I think this question
would be better directed to Insight users.
Ian
next prev parent reply other threads:[~2009-06-29 21:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 8:08 田晓南
2009-06-19 11:56 ` Paolo Bonzini
2009-06-24 9:35 ` daniel.tian
2009-06-24 9:36 ` Dave Korn
2009-06-24 9:37 ` Paolo Bonzini
2009-06-24 10:16 ` Dave Korn
2009-06-25 18:43 ` Jeff Law
2009-06-29 10:40 ` 答复: " daniel.tian
2009-07-01 1:57 ` Jeff Law
2009-06-29 10:52 ` daniel.tian
2009-06-29 21:11 ` Ian Lance Taylor [this message]
2009-06-30 6:20 ` How " Jim Wilson
2009-06-30 14:22 ` daniel.tian
2009-07-01 2:05 ` Jeff Law
[not found] <5885251a0906190727p301b9122k7dcd235dcdd082a4@mail.gmail.com>
2009-06-22 1:56 ` daniel.tian
2009-06-22 11:21 ` Dave Korn
2009-06-24 12:42 daniel tian
2009-06-25 19:18 ` Jeff Law
2009-07-01 3:02 daniel.tian
2009-07-01 6:14 ` Jeff Law
2009-07-02 3:06 ` daniel.tian
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m37hyu3g6c.fsf@google.com \
--to=iant@google.com \
--cc=daniel.tian@mavrixtech.com.cn \
--cc=gcc@gcc.gnu.org \
--cc=law@redhat.com \
--cc=peng.zheng@mavrixtech.com \
--cc=thomas.liau@mavrixtech.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).