Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: "H.J. Lu" <hjl.tools@gmail.com>,
	Mark Kettenis <mark.kettenis@xs4all.nl>,
	 	gdb-patches@sourceware.org
Subject: Re: PATCH: PATCH: Add builtin floating point types
Date: Sun, 07 Feb 2010 22:25:00 -0000	[thread overview]
Message-ID: <6dc9ffc81002071425y74b5bb8eha47bacc6f1d2a33e@mail.gmail.com> (raw)
In-Reply-To: <20100207221444.GA5399@caradoc.them.org>

On Sun, Feb 7, 2010 at 2:14 PM, Daniel Jacobowitz <dan@codesourcery.com> wrote:
> On Sun, Feb 07, 2010 at 02:00:36PM -0800, H.J. Lu wrote:
>> Is there a way to call i387_ext_type from  target-descriptions.c?
>> Otherwise,  XML target description will create multiple i386_ext
>> types and won't work for x86 since x86 requires single i386_ext
>> type per arch.
>
> Maybe the common code could cache the created types?
>

I need a place to hold the created type in the common code.
When do I put it?

Thanks.


-- 
H.J.


  reply	other threads:[~2010-02-07 22:25 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-05  1:15 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 [this message]
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
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=6dc9ffc81002071425y74b5bb8eha47bacc6f1d2a33e@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --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