From: Jim Blandy <jimb@codesourcery.com>
To: Maxim Grigoriev <maxim@tensilica.com>
Cc: gdb-patches@sources.redhat.com,
Bob Wilson <bwilson@tensilica.com>,
chris Zankel <zankel@tensilica.com>
Subject: Re: Xtensa port
Date: Fri, 22 Sep 2006 20:32:00 -0000 [thread overview]
Message-ID: <m3odt74p5x.fsf@codesourcery.com> (raw)
In-Reply-To: <45142A88.7000805@hq.tensilica.com> (Maxim Grigoriev's message of "Fri, 22 Sep 2006 11:25:12 -0700")
Maxim Grigoriev <maxim@tensilica.com> writes:
> Basic Xtensa port. It doesn't include any targets. The next step will be
> a submission of "xtensa*-*-linux" target. It will include gdbserver port and
> everything else necessary to debug Xtensa code on this target.
Thanks for the contribution!
I haven't looked at the code closely, but I have a few questions.
- Where does xtensa-config.h come from?
- Does xtensa-config.c need to be listed in ALLDEPFILES as well?
- I don't see anything that actually plugs in xtensa-linux-tdep.o.
Should that be kept out until the linux target is ready?
- In your DejaGnu config files, there is a way to tell GDB not to run
tests that depend on the inferior being able to do I/O; this is used
to run the tests against embedded systems that don't implement the
semi-hosting protocol packets, like yours. Look for uses of
'gdb_skip_stdio_test'.
- Can you explain more about the differences between the
Xtensa-generated DWARF and what GDB expects? Ideally, GDB should
accept DWARF from any compiler, but because DWARF is so flexible
it's easy for inappropriate expectations to creep in.
next prev parent reply other threads:[~2006-09-22 20:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-22 18:25 Maxim Grigoriev
2006-09-22 18:52 ` Michael Snyder
2006-09-22 19:11 ` Maxim Grigoriev
2006-09-22 20:11 ` Michael Snyder
2006-09-22 21:48 ` Maxim Grigoriev
2006-09-22 23:53 ` Daniel Jacobowitz
2006-09-22 19:07 ` Daniel Jacobowitz
2006-09-22 19:39 ` Maxim Grigoriev
2006-09-22 20:32 ` Jim Blandy [this message]
2006-09-22 23:59 ` Maxim Grigoriev
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=m3odt74p5x.fsf@codesourcery.com \
--to=jimb@codesourcery.com \
--cc=bwilson@tensilica.com \
--cc=gdb-patches@sources.redhat.com \
--cc=maxim@tensilica.com \
--cc=zankel@tensilica.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