Re: short float ???
- From: Lew Pitcher <lpitcher@xxxxxxxxxxxx>
- Date: Wed, 01 Jul 2009 11:17:01 -0400
On July 1, 2009 11:01, in comp.std.c, Giacomo Catenazzi (cate@xxxxxxxxxx)
wrote:
jacob navia wrote:
Hi
In a previous message I asked this question but it got swamped by the
discussion about vector extensions (that has degenerated into
discussions about everything else, as it happens when the people in
comp.lang.c come into play)
Specifically I want to suggest that we use the combination of
short float
to describe a floating point data type of half precision (16 bits)
This format is used in the NVIDIA graphic cards and will be available
in the x86 instruction set beginning 2010.
16-bit for a floats seems too small.
Could you give us the precision, the range and expected use
of such floats?
My concern are about the use:
- speed: but in this case C will use double precision calculations,
thus removing the speed advantage
- size: (to store huge amount of data).
The second one requires very few changes in C, but the first one
(which I think it is the intention) give big problem to C
language.
I have similar questions that I'd like Jacob to address.
Jacob: you mention that "this format is used in the NVIDIA graphic cards,
and will be available in the x86 instruction set beginning 2010".
1) /Which/ format is "this format"? Is the floatingpoint format used in
NVIDIA cards the /same/ format as will be available in the x86
instructionset? What about other GPUs and processors that support a "short
floatingpoint" format natively?
2) Although those specific platforms are fairly popular, they do not make up
the entirety of the C platform universe. Can you expand on why a "short
floatingpoint" format tailored to these platforms, rather than, say, a
floatingpoint format tailored to the existing RISC or FPGA/embedded
platforms available now?
3) Do you intend that C perform computations with your proposed "short
float", or will standard promotion rules apply and computations be
performed in "long float" equivalents (after promotion)? If so, then what
benefit does "short float" provide on the platforms you mentioned?
4) In a previous post, you replied (my summary, not your actual words) that
other changes to the C language that would be necessitated by your
proposed "short float" would be trivial. To me, /someone/ has to do the
actual dog-work of detailing those changes, and making a proposal as to
what the standard should say, and that /someone/ should be the person who
makes the initial "short float" proposal that initiated the changes. Are
you prepared to flesh out your proposal, including guidance on how all
those other details should look? If not, then /who/?
--
Lew Pitcher
Master Codewright & JOAT-in-training | Registered Linux User #112576
http://pitcher.digitalfreehold.ca/ | GPG public key available by request
---------- Slackware - Because I know what I'm doing. ------
.
- Follow-Ups:
- Re: short float ???
- From: jacob navia
- Re: short float ???
- References:
- Re: short float ???
- From: Giacomo Catenazzi
- Re: short float ???
- Prev by Date: Re: short float ???
- Next by Date: Re: short float ???
- Previous by thread: Re: short float ???
- Next by thread: Re: short float ???
- Index(es):
Relevant Pages
|
Loading