Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Phil Edwards <phil@jaj.com>, Richard Earnshaw <rearnsha@arm.com>
Cc: gdb@sources.redhat.com
Subject: Re: Your change breaks GDB for ARM
Date: Fri, 21 Nov 2003 16:31:00 -0000	[thread overview]
Message-ID: <3FBE3DC2.8030007@redhat.com> (raw)
In-Reply-To: <20031121075532.GA13535@disaster.jaj.com>

A not so trivial find/grep shows:

cagney@nettle$ frep target_byte_order
arch-utils.c:376:/* ``target_byte_order'' is only used when non- multi-arch.
arch-utils.c:383:static int target_byte_order = BFD_ENDIAN_BIG;
arch-utils.c:384:static int target_byte_order_auto = 1;
arch-utils.c:389:  if (target_byte_order_auto)
arch-utils.c:392:    return target_byte_order;
arch-utils.c:412:  if (target_byte_order_auto)
arch-utils.c:425:      target_byte_order_auto = 1;
arch-utils.c:430:      target_byte_order_auto = 0;
arch-utils.c:439:      target_byte_order_auto = 0;
arch-utils.c:730:      && !target_byte_order_auto

which are all perfectly fine.  As for:

remote-rdp.c:355:                   target_byte_order = BFD_ENDIAN_LITTLE;
remote-rdp.c:359:                   target_byte_order = BFD_ENDIAN_BIG;

oops, missed them.  I guess I could #ifdef them out (richard?).  Those 
assignments haven't done anything useful since 2002-02-08 when the arm 
became multi-arch partial.

Andrew


  reply	other threads:[~2003-11-21 16:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-21  7:55 Phil Edwards
2003-11-21 16:31 ` Andrew Cagney [this message]
2003-11-21 16:49   ` Richard Earnshaw
2003-11-21 18:04     ` Andrew Cagney
2003-11-23 10:48       ` Phil Edwards

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=3FBE3DC2.8030007@redhat.com \
    --to=ac131313@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=phil@jaj.com \
    --cc=rearnsha@arm.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