From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: Re: RFC: A change to the way we initialize new gdbarches
Date: Thu, 19 Oct 2006 20:00:00 -0000 [thread overview]
Message-ID: <20061019200028.GB1225@adacore.com> (raw)
In-Reply-To: <20061018204802.GA20757@nevyn.them.org>
> 2006-10-18 Daniel Jacobowitz <dan@codesourcery.com>
>
> * arch-utils.c (target_byte_order_user): Renamed from
> target_byte_order.
> (target_byte_order_auto, selected_byte_order): Removed.
> (show_endian): Check target_byte_order_user.
> (set_endian): Always update the architecture. Set
> target_byte_order_user after success.
> (target_architecture_auto): Removed.
> (target_architecture_user): New.
> (selected_architecture_name, show_architecture): Check it.
> (set_architecture): Set target_architecture_user after success.
> (gdbarch_from_bfd): Check the argument.
> (default_byte_order): New.
> (initialize_current_architecture): Set the global default
> architecture and endianness.
> (gdbarch_info_fill): Remove GDBARCH argument. Do not check the
> previous architecture. Use exec_bfd, global selected architecture
> and endianness, and global defaults.
> * arch-utils.h (selected_byte_order): Remove prototype.
> (gdbarch_info_fill): Update.
> * exec.c (exec_file_attach): Update the architecture after removing
> the current file.
> * gdbarch.sh: Update comments.
> (find_arch_by_info): Remove OLD_GDBARCH argument. Update call to
> gdbarch_info_fill.
> (gdbarch_find_by_info): Update call to find_arch_by_info.
> * gdbarch.h, gdbarch.c: Regenerated.
> * remote-sim.c (gdbsim_open): Use TARGET_BYTE_ORDER.
FWIW, I had a look a this change. I like the approach.
--
Joel
next prev parent reply other threads:[~2006-10-19 20:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 23:10 Daniel Jacobowitz
2006-10-05 20:06 ` Mark Kettenis
2006-10-05 20:25 ` Daniel Jacobowitz
2006-10-18 20:48 ` Daniel Jacobowitz
2006-10-19 20:00 ` Joel Brobecker [this message]
2006-11-09 19:50 ` [rfa/doc] " Daniel Jacobowitz
2006-11-09 21:23 ` Eli Zaretskii
2006-11-10 15:33 ` Eli Zaretskii
2006-11-10 16:56 ` Daniel Jacobowitz
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=20061019200028.GB1225@adacore.com \
--to=brobecker@adacore.com \
--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