Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Phil Edwards <phil@jaj.com>
To: gdb@sources.redhat.com, cagney@redhat.com
Subject: Your change breaks GDB for ARM
Date: Fri, 21 Nov 2003 07:55:00 -0000	[thread overview]
Message-ID: <20031121075532.GA13535@disaster.jaj.com> (raw)

(I am not subscribed to this list.)


This change

  2003-11-13  Andrew Cagney  <cagney@redhat.com>

    * arch-utils.h (selected_architecture_name): Declare.
    (selected_byte_order): Declare.
    * arch-utils.c (selected_byte_order): New function.
    (selected_architecture_name): New function.
    (target_architecture_auto): Make static.
    (set_architecture_string): Make static.
    (target_byte_order): Make static.
    (target_byte_order_auto): Make static.
    * gdbarch.sh (TARGET_BYTE_ORDER, TARGET_ARCHITECTURE): Delete
    non-multi-arch definition.
    (TARGET_ARCHITECTURE_AUTO, TARGET_BYTE_ORDER_AUTO): Delete.
    (target_byte_order, target_architecture): Delete declaration.
    (target_byte_order_auto, target_architecture_auto): Ditto.
    * gdbarch.h: Re-generate.
    * remote-sim.c (gdbsim_open): Use "selected_architecture_name" and
    "selected_byte_order".

didn't get enough testing.  As a trivial search shows,

    fenric 57% cd gdb
    fenric 58% grep -l target_byte_order *.c
    arch-utils.c
    remote-rdp.c
    fenric 59%

this variable is still being used outside of the file where you made
it static, and now GDB will not build for arm-elf targets, which use
remote-rdp.c.

I looked very briefly at the new code, but as remote-rdp.c is setting
target_byte_order, not reading it, there is no obvious change I could make.
Please fix this breakage soon.


Phil


             reply	other threads:[~2003-11-21  7:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-21  7:55 Phil Edwards [this message]
2003-11-21 16:31 ` Andrew Cagney
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=20031121075532.GA13535@disaster.jaj.com \
    --to=phil@jaj.com \
    --cc=cagney@redhat.com \
    --cc=gdb@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