From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: drow@false.org (Daniel Jacobowitz)
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA][2/5] New port: Cell BE SPU (valops.c fix)
Date: Wed, 22 Nov 2006 19:55:00 -0000 [thread overview]
Message-ID: <200611221955.kAMJt2MT006973@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20061122192845.GA12105@nevyn.them.org> from "Daniel Jacobowitz" at Nov 22, 2006 02:28:45 PM
Daniel Jacobowitz wrote:
> On Wed, Nov 22, 2006 at 11:25:48AM -0800, Jim Blandy wrote:
> > Or, possibly another gdbarch method, VALUE_TO_REGISTER_BITFIELD, which
> > can be left unset, provoking an internal error in value_assign?
>
> I'm not even quite sure how bitfields come into it. The register
> type's a builtin_type_vec128.
The problem occurs if there is a source-level variable of bitfield type
that currently resides in such a register, and the GDB user attempts to
assign to that variable.
I guess one problem here is that there's two different problems intermixed
here:
- if an integral type (possibly bitfield) resides in a vector register,
which parts of the vector register can I find it at (that's the platform
specific part)
- where within the bitfield is the particular element I want to access
(that's the generic part)
Maybe the best solution would be for GDB common code to call
VALUE_TO_REGISTER / REGISTER_TO_VALUE to solve the first problem,
but still solve the second problem in common code.
Otherwise every target would have to implement all the bitfield fiddling
separately -- I'm not sure this is required.
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2006-11-22 19:55 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-11 18:38 Ulrich Weigand
2006-11-22 14:15 ` [PING] " Ulrich Weigand
2006-11-22 14:23 ` Daniel Jacobowitz
2006-11-22 19:25 ` Jim Blandy
2006-11-22 19:28 ` Daniel Jacobowitz
2006-11-22 19:55 ` Ulrich Weigand [this message]
2006-11-22 20:30 ` Daniel Jacobowitz
2006-11-22 20:43 ` Ulrich Weigand
2006-11-22 20:57 ` Daniel Jacobowitz
2006-11-22 22:13 ` Ulrich Weigand
2006-11-22 22:48 ` Daniel Jacobowitz
2006-11-23 13:57 ` Ulrich Weigand
2006-11-23 16:16 ` Daniel Jacobowitz
2006-11-23 17:55 ` Ulrich Weigand
2006-11-23 19:59 ` Mark Kettenis
2006-11-24 2:08 ` Daniel Jacobowitz
2006-11-24 15:51 ` Ulrich Weigand
2006-11-28 14:56 ` Daniel Jacobowitz
2006-11-27 19:31 ` Jim Blandy
2006-11-27 22:06 ` Ulrich Weigand
2006-11-27 22:31 ` Jim Blandy
2006-11-27 23:23 ` Ulrich Weigand
2006-11-27 23:59 ` Jim Blandy
2006-11-28 0:01 ` Daniel Jacobowitz
2006-12-06 16:29 ` Ulrich Weigand
2006-12-06 16:43 ` Daniel Jacobowitz
2006-12-06 17:10 ` Ulrich Weigand
2006-12-06 17:12 ` Daniel Jacobowitz
2006-12-07 6:34 ` Vladimir Prus
2006-12-06 21:21 ` Jim Blandy
2006-12-06 22:02 ` Daniel Jacobowitz
2006-12-06 23:24 ` Jim Blandy
2006-12-06 23:16 ` Ulrich Weigand
2006-12-06 23:39 ` Jim Blandy
2006-12-08 15:50 ` Ulrich Weigand
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=200611221955.kAMJt2MT006973@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
/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