From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [rfc] Tighten meaning of gdbarch_convert_register_p
Date: Wed, 24 Oct 2007 20:41:00 -0000 [thread overview]
Message-ID: <20071024202912.GN10943@caradoc.them.org> (raw)
In-Reply-To: <20071017140308.GA15513@caradoc.them.org>
On Wed, Oct 17, 2007 at 10:03:08AM -0400, Daniel Jacobowitz wrote:
> 2007-10-17 Daniel Jacobowitz <dan@codesourcery.com>
>
> * amd64-tdep.c (amd64_convert_register_p): Delete.
> (amd64_init_abi): Use i387_convert_register_p.
> * alpha-tdep.c (alpha_convert_register_p): Return zero for
> eight byte types.
> (alpha_register_to_value, alpha_value_to_register): Do not handle
> eight byte types.
> * i386-tdep.c (i386_convert_register_p): Use i387_convert_register_p.
> * i387-tdep.c (i387_convert_register_p): New.
> (i387_register_to_value, i387_value_to_register): Update comments.
> * i387-tdep.h (i387_convert_register_p): Declare.
> * ia64-tdep.c (ia64_convert_register_p): Return zero for
> builtin_type_ia64_ext.
> (ia64_gdbarch_init): Do not initialize builtin_type_ia64_ext here.
> (_initialize_ia64_tdep): Initialize builtin_type_ia64_ext here.
> * m68k-tdep.c (m68k_convert_register_p): Return zero for
> builtin_type_m68881_ext.
> (m68k_register_to_value, m68k_value_to_register): Update comments.
>
> * gdbint.texinfo (Register and Memory Data, Target Conditionals):
> Document that gdbarch_convert_register_p should return zero for no-op
> conversions.
I checked this in, along with some changelog fixes.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-10-24 20:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 18:32 Daniel Jacobowitz
2007-10-19 4:19 ` Joel Brobecker
2007-10-24 20:41 ` Daniel Jacobowitz [this message]
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=20071024202912.GN10943@caradoc.them.org \
--to=drow@false.org \
--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