From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: deuling@de.ibm.com (Markus Deuling)
Cc: gdb-patches@sourceware.org (GDB Patches),
eliz@gnu.org (Eli Zaretskii),
drow@false.org (Daniel Jacobowitz)
Subject: Re: [patch] Remove BITS_BIG_ENDIAN from defs.h
Date: Tue, 15 Jan 2008 21:01:00 -0000 [thread overview]
Message-ID: <200801152101.m0FL12x2012798@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <478C76F5.2000402@de.ibm.com> from "Markus Deuling" at Jan 15, 2008 10:03:49 AM
Markus Deuling wrote:
> @@ -251,6 +252,7 @@ struct gdbarch startup_gdbarch =
> /*per-architecture data-pointers and swap regions */
> 0, NULL, NULL,
> /* Multi-arch values */
> + 0, /* bits_big_endian */
> 8 * sizeof (short), /* short_bit */
> 8 * sizeof (int), /* int_bit */
> 8 * sizeof (long), /* long_bit */
The "static default" of 0 for bits_big_endian is inconsistent
with the static default of BFD_ENDIAN_BIG for byte_order ...
> +# The bit byte-order has to do just with numbering of bits in debugging symbols
> +# and such. Conceptually, it's quite separate from byte/word byte order.
> +v:int:bits_big_endian:::0:(gdbarch->byte_order == BFD_ENDIAN_BIG)::0
... so I guess this should preferably be:
v:int:bits_big_endian:::1:(gdbarch->byte_order == BFD_ENDIAN_BIG)::0
Otherwise, this patch is OK, but please commit only together with ...
>I tested this patch on both Little and Big Endian machine (x86/ppc) without regression.
>If this patch is ok I'll post another one for the documentation. Ok to commit?
... the documentation patch (once that is approved).
Thanks,
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:[~2008-01-15 21:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 18:20 Markus Deuling
2008-01-11 19:24 ` Daniel Jacobowitz
2008-01-11 20:59 ` Eli Zaretskii
2008-01-14 18:11 ` Ulrich Weigand
2008-01-15 9:06 ` Markus Deuling
2008-01-15 21:01 ` Ulrich Weigand [this message]
2008-01-16 5:59 ` Markus Deuling
2008-01-16 18:43 ` Eli Zaretskii
2008-01-17 7:09 ` Markus Deuling
2008-01-18 16:21 ` Eli Zaretskii
2008-01-18 17:08 ` Markus Deuling
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=200801152101.m0FL12x2012798@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=deuling@de.ibm.com \
--cc=drow@false.org \
--cc=eliz@gnu.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