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

On Sun, Feb 7, 2010 at 1:52 PM, Mark Kettenis <mark.kettenis@xs4all.nl> wrote:
>> Date: Thu, 4 Feb 2010 17:14:47 -0800
>> From: "H.J. Lu" <hongjiu.lu@intel.com>
>>
>> I am resending this patch. The motivation is I am working on x86 xml
>> target descriptions.  x86 has i387_ext type. I added
>>
>>   case TDESC_TYPE_I387_EXT:
>>      return arch_float_type (gdbarch, -1, "builtin_type_i387_ext",
>>                              floatformats_i387_ext);
>>
>> to tdesc_gdb_type. I would up 8 i387_ext types at 8 different addresses
>> with the same bits. x86 does
>>
>> if (i386_fp_regnum_p (gdbarch, regnum))
>>    {
>>      /* Floating point registers must be converted unless we are
>>         accessing them in their hardware type.  */
>>      if (type == i387_ext_type (gdbarch))
>>        return 0;
>>      else
>>        return 1;
>>    }
>>
>> It expects 2  i387_ext types should have the same address.  This
>> patch caches ieee_single, ieee_double and i387_ext. OK to install?
>
> Sorry, but I don't like this diff.  At the very least, keep the
> i387_ext_type() function around.  It makes the diff far less invasive.

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.

Thanks.


-- 
H.J.


  reply	other threads:[~2010-02-07 22:00 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 [this message]
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
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=6dc9ffc81002071400u5bad1726v93330aeb38246143@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