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: Mon, 08 Feb 2010 18:56:00 -0000 [thread overview]
Message-ID: <6dc9ffc81002081056m444936f1hd2cc12183addaf3c@mail.gmail.com> (raw)
In-Reply-To: <20100208141423.GA26959@caradoc.them.org>
On Mon, Feb 8, 2010 at 6:14 AM, Daniel Jacobowitz <dan@codesourcery.com> wrote:
> On Sun, Feb 07, 2010 at 09:16:25PM -0800, H.J. Lu wrote:
>> in gdbtypes.c. struct arch_type will have
>>
>> struct type *arch_ieee_single;
>> struct type *arch_ieee_double;
>> struct type *arch_i387_ext;
>>
>> They will be lazy initialized. I thought that was what you suggested.
>
> This hasn't changed anything; it still has to know about i387_ext.
>
> There are at least two options. We could use a per-gdbarch hash table
> to cache the result of arch_float_type (in arch_float_type, not in its
> caller). Or we could put the cache in tdesc_gdb_type, which is
> probably easier.
A patch is posted at
http://sourceware.org/ml/gdb-patches/2010-02/msg00214.html
Thanks.
--
H.J.
next prev parent reply other threads:[~2010-02-08 18:56 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
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 [this message]
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=6dc9ffc81002081056m444936f1hd2cc12183addaf3c@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