Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: brobecker@adacore.com (Joel Brobecker)
Cc: ken@linux.vnet.ibm.com (Ken Werner), gdb-patches@sourceware.org
Subject: Re: [patch, libiberty, gdb] IEEE 754 half floating-point format
Date: Tue, 14 Dec 2010 16:10:00 -0000	[thread overview]
Message-ID: <201012141610.oBEGA5r2029793@d06av02.portsmouth.uk.ibm.com> (raw)
In-Reply-To: <20101118174427.GG2634@adacore.com> from "Joel Brobecker" at Nov 18, 2010 09:44:27 AM

Joel Brobecker wrote:
> > include/ChangeLog:
> > 
> > 2010-07-02  Ken Werner  <ken.werner@de.ibm.com>
> > 
> > 	* gfloatformat.h (floatformat_ieee_half_big): Add declaration.
>           ^^^ typo
> > 	(floatformat_ieee_half_little): Likewise.
> > 
> > libiberty/ChangeLog:
> > 
> > 2010-07-02  Ken Werner  <ken.werner@de.ibm.com>
> > 
> > 	* floatformat.c (floatformat_ieee_half_big): New variable.
> > 	(floatformat_ieee_half_little): Likewise.
> 
> This part should be submitted to GCC, I think?
> 
> > 2010-07-02  Ken Werner  <ken.werner@de.ibm.com>
> > 
> > 	* gdbtypes.h (floatformats_ieee_half): Add declaration.
> > 	* gdbtypes.c (floatformats_ieee_half): New variable.
> > 	* doublest.c (floatformat_from_length): Set format to
> > 	gdbarch_half_format if length matches.
> > 	* gdbarch.sh (half_bit): New architecture method.
> > 	(half_format): Likewise.
> > 	* gdbarch.h: Regenerate.
> > 	* gdbarch.c: Likewise.
> 
> My only comment regarding this part of the patch is that "half_bit"
> and "half_format" isn't very intuitive. Perhaps that's more obvious
> to someone who programs in OpenCL if "half" is a type name? For
> the other arch routines, the routine name makes it clear that it's
> about floating point types, because it contains a name that is
> clearly associated to floats (float, double, long double).  What
> about using "half_float_bit" and "half_float_format"?
> 
> What do others think?

Note that I had already approved this patch back in July, after
the libiberty part was approved by DJ Delorie, so everything is
already committed ...

Of course, we could still change the name of the gdbarch callbacks
if you think this would be more intuitive.

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


  reply	other threads:[~2010-12-14 16:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-02 16:59 Ken Werner
2010-07-02 17:11 ` Ken Werner
2010-07-02 18:47   ` DJ Delorie
2010-07-06 13:06 ` Ulrich Weigand
2010-11-18 17:44 ` Joel Brobecker
2010-12-14 16:10   ` Ulrich Weigand [this message]
2010-12-15  5:07     ` Joel Brobecker

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=201012141610.oBEGA5r2029793@d06av02.portsmouth.uk.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=ken@linux.vnet.ibm.com \
    /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