From: Daniel Jacobowitz <drow@false.org>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: dwarf2-frame.c read_reg problems, again ...
Date: Wed, 31 Oct 2007 19:12:00 -0000 [thread overview]
Message-ID: <20071031184240.GA18037@caradoc.them.org> (raw)
In-Reply-To: <200710311837.l9VIb3RY010625@d12av02.megacenter.de.ibm.com>
On Wed, Oct 31, 2007 at 07:37:03PM +0100, Ulrich Weigand wrote:
> So I don't mind making them unsigned again. How would that work
> with the XML definitions? Do you have to add an explicit type
> attribute everywhere?
That's right. The default is "int", which is signed.
When I was designing the format I thought up a pile of clever ways to
make the format easier to write and more concise, like repeating
register sets. Of course, they also make it harder to parse and
more complicated to document. So I haven't implemented any of them
:-)
> I'd say targets like that should be able to define a proper conversion to
> builtin_type_void_data_ptr via convert_register or value_from_register
> for that specific register.
>
> Alternatively, if builtin_type_void_data_ptr is in fact the wrong
> type to describe a CFA on some weird platform, we could allow the
> gdbarch to define the type to be used for this.
That's an interesting idea...
I don't have a helpful opinion about this particular case, I'm afraid.
I just don't want to break whatever Michael was working with, or
MIPS again (which requires sign extension here).
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-10-31 18:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-31 2:18 Ulrich Weigand
2007-10-31 4:47 ` Daniel Jacobowitz
2007-10-31 18:56 ` Ulrich Weigand
2007-10-31 19:12 ` Daniel Jacobowitz [this message]
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=20071031184240.GA18037@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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