From: Daniel Jacobowitz <dan@codesourcery.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: GDB <gdb-patches@sourceware.org>,
Mark Kettenis <mark.kettenis@xs4all.nl>
Subject: Re: PATCH: Cache types from target description
Date: Wed, 10 Feb 2010 18:38:00 -0000 [thread overview]
Message-ID: <20100210183800.GA25489@caradoc.them.org> (raw)
In-Reply-To: <20100209154513.GA27404@lucon.org>
On Tue, Feb 09, 2010 at 07:45:13AM -0800, H.J. Lu wrote:
> 2010-02-09 H.J. Lu <hongjiu.lu@intel.com>
>
> * target-descriptions.c (tdesc_type): Add TDESC_TYPE_I387_EXT,
> TDESC_TYPE_I386_EFLAGS and TDESC_TYPE_I386_MXCSR.
> (tdesc_predefined_types): Add i387_ext, i386_eflags and
> i386_mxcsr.
> (tdesc_find_type): New.
> (tdesc_gdb_type): Use tdesc_find_type. Handle TDESC_TYPE_I387_EXT,
> TDESC_TYPE_I386_EFLAGS and TDESC_TYPE_I386_MXCSR.
>
> * target-descriptions.h (tdesc_find_type): New.
This is OK. I am not happy having the flag types in this file, but
I don't see a better way yet. Really they should be described in the
XML file!
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2010-02-10 18:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 1:15 PATCH: PATCH: Add builtin floating point types H.J. Lu
2010-02-07 21:52 ` Mark Kettenis
2010-02-07 22:00 ` H.J. Lu
2010-02-07 22:14 ` Daniel Jacobowitz
2010-02-07 22:25 ` H.J. Lu
2010-02-07 23:03 ` H.J. Lu
2010-02-07 23:08 ` Daniel Jacobowitz
2010-02-08 2:17 ` H.J. Lu
2010-02-08 4:17 ` Daniel Jacobowitz
2010-02-08 5:16 ` H.J. Lu
2010-02-08 14:14 ` Daniel Jacobowitz
2010-02-08 14:56 ` H.J. Lu
2010-02-08 18:56 ` H.J. Lu
2010-02-08 18:55 ` PATCH: Cache types from target description H.J. Lu
2010-02-09 15:45 ` H.J. Lu
2010-02-09 18:47 ` Eli Zaretskii
2010-02-09 18:56 ` H.J. Lu
2010-02-10 18:38 ` Daniel Jacobowitz [this message]
2010-02-10 20:54 ` Mark Kettenis
2010-02-10 21:01 ` 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=20100210183800.GA25489@caradoc.them.org \
--to=dan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=mark.kettenis@xs4all.nl \
/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