From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Daniel Jacobowitz <drow@false.org>,
Ulrich Weigand <uweigand@de.ibm.com>,
Doug Evans <dje@google.com>
Subject: Re: Per-type architecture (Re: [10/15] Basic value access routines)
Date: Tue, 23 Jun 2009 14:02:00 -0000 [thread overview]
Message-ID: <200906231503.32497.pedro@codesourcery.com> (raw)
In-Reply-To: <20090623134938.GA12312@caradoc.them.org>
On Tuesday 23 June 2009 14:49:38, Daniel Jacobowitz wrote:
> On Tue, Jun 23, 2009 at 02:41:22AM +0200, Ulrich Weigand wrote:
> > - for values of bitfield type, the bitfield byte order (as you mention)
>
> We don't actually need the architecture for this, given the type. But
> that's only because the way we record this in types requires the
> architecture when building the type; I've seriously considered
> rearranging it so that the type was architecture neutral and the value
> architecture dependent. But it seems too fragile to touch without a
> better reason...
Would sharing of objfiles between inferiors be a reason? I can picture
GDB debugging two inferiors with (maybe slightly or not) different
gdbarchs loading the same shared object.
--
Pedro Alves
next prev parent reply other threads:[~2009-06-23 14:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 15:20 [10/15] Basic value access routines Ulrich Weigand
2009-06-15 16:35 ` Doug Evans
2009-06-15 16:59 ` Ulrich Weigand
2009-06-22 20:32 ` Per-type architecture (Re: [10/15] Basic value access routines) Ulrich Weigand
2009-06-22 20:59 ` Daniel Jacobowitz
2009-06-23 0:41 ` Ulrich Weigand
2009-06-23 13:49 ` Daniel Jacobowitz
2009-06-23 14:02 ` Pedro Alves [this message]
2009-06-23 17:06 ` Ulrich Weigand
2009-06-23 17:30 ` Daniel Jacobowitz
2009-06-23 15:55 ` Doug Evans
2009-06-23 16:42 ` Mark Kettenis
2009-06-23 16:53 ` Daniel Jacobowitz
2009-06-23 16:57 ` Ulrich Weigand
2009-06-23 17:36 ` Doug Evans
2009-06-24 15:31 ` [10/15] Basic value access routines Tom Tromey
2009-06-24 15:46 ` Daniel Jacobowitz
2009-06-24 16:26 ` Doug Evans
2009-06-24 19:41 ` Tom Tromey
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=200906231503.32497.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=dje@google.com \
--cc=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