From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Eliminate TARGET_BYTE_ORDER_SELECTABLE
Date: Sat, 19 Jan 2002 08:57:00 -0000 [thread overview]
Message-ID: <3C49A566.1060508@cygnus.com> (raw)
In-Reply-To: <20020119094718.A1404@nevyn.them.org>
> On Sat, Jan 19, 2002 at 12:58:36AM -0500, Andrew Cagney wrote:
>
>> Hello,
>>
>> All multi-arch targets (yep, including the i386) allow the byte order to
>> be selected at run time. This means that the macro
>> TARGET_BYTE_ORDER_SELECTABLE which was used by non-multi-arch targets is
>> obsolete.
>>
>> The attached patch eliminates that macro. I've tested it on a
>> multi-arch target and I don't think it breaks non-multi-arch targets.
>>
>> Anyway, I intend committing this in a few days.
>> Andrew
>
>
> Hmm, I don't know. Do we really want to do this? This allows, for
> instance, 'set endian big' on i386. That may someday make someone
> think that GDB supports such a beast, on the off chance one is ever
> made.
Ah, but we live in dangerous times :-)
TARGET_BYTE_ORDER_SELECTABLE, TARGET_BYTE_ORDER_SELECTABLE_P and even
TARGET_BYTE_ORDER_DEFAULT are all there just to prop up old pre-
multi-arch targets. They are not used by a multi-arch GDB.
All multi-arch architectures allow both big and little byte orders
(regardless of what the spec says). This lets the user do things like:
(gdb) print network_structure
(gdb) set endian big
(gdb) print network_structure
enjoy,
Andrew
next prev parent reply other threads:[~2002-01-19 16:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-18 21:59 Andrew Cagney
2002-01-19 6:47 ` Daniel Jacobowitz
2002-01-19 8:06 ` Michael Snyder
2002-01-19 8:57 ` Andrew Cagney [this message]
2002-01-19 9:00 ` Daniel Jacobowitz
2002-01-20 10:33 ` Andrew Cagney
2002-01-20 10:36 ` Daniel Jacobowitz
2002-01-20 11:00 ` Andrew Cagney
2002-01-20 11:05 ` Daniel Jacobowitz
2002-01-20 11:18 ` Andrew Cagney
2002-01-20 0:30 ` Eli Zaretskii
2002-01-20 11:32 ` Andrew Cagney
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=3C49A566.1060508@cygnus.com \
--to=ac131313@cygnus.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.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