Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: "Maciej W. Rozycki" <macro@imgtec.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PING][PATCH] arch-utils: Make the last endianness actually chosen sticky
Date: Tue, 08 Nov 2016 22:50:00 -0000	[thread overview]
Message-ID: <CADPb22TBdpRUJPGzy4wE3ff0C-K0pniAKTVbpwjDa1ycTJAGqg@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.17.1611080840340.10580@tp.orcam.me.uk>

On Tue, Nov 8, 2016 at 12:45 AM, Maciej W. Rozycki <macro@imgtec.com> wrote:
> On Fri, 14 Oct 2016, Maciej W. Rozycki wrote:
>
>>       gdb/
>>       * arch-utils.c (gdbarch_info_fill): Set `default_byte_order' to
>>       the endianness selected.
>>
>>       gdb/testsuite
>>       * gdb.base/endian.exp: New test.
>>       * gdb.base/endian.c: New test source.
>
>  Can I ask for <https://patchwork.sourceware.org/patch/16504/> to be
> reviewed?

Hi.

This is fine with me.
[I can imagine oddities if someone was doing multi-inferior debugging
with different endiannesses, but that's a rare situation, and I don't
think any oddities if they exist are killers.]

I tested it on amd64-linux just as a sanity check.

I think a NEWS entry is required.

I'm kinda thinking an addition to the "Choosing Target Byte Order"
would be nice, but it's not mandatory. [If we do so, I think to do it
right you would have to document a whole lot more than just
this simple addition, and I don't like imposing on you that
burden. If you want to take it on, great of course.
But to me it's not necessary for this patch to go in.]


  parent reply	other threads:[~2016-11-08 22:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-14 13:12 [PATCH] " Maciej W. Rozycki
     [not found] ` <alpine.DEB.2.20.17.1611080840340.10580@tp.orcam.me.uk>
2016-11-08 22:50   ` Doug Evans [this message]
2018-05-30 20:55     ` [PATCH v2] " Maciej W. Rozycki
2018-05-31  8:39       ` Eli Zaretskii
2018-05-31 14:46         ` Maciej W. Rozycki
2018-05-31 17:12       ` Doug Evans via gdb-patches

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=CADPb22TBdpRUJPGzy4wE3ff0C-K0pniAKTVbpwjDa1ycTJAGqg@mail.gmail.com \
    --to=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=macro@imgtec.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