Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.std.c > #6006 > unrolled thread

short float

Started byPhilipp Klaus Krause <pkk@spth.de>
First post2019-10-28 11:58 +0100
Last post2020-12-13 13:42 +0100
Articles 5 — 4 participants

Back to article view | Back to comp.std.c


Contents

  short float Philipp Klaus Krause <pkk@spth.de> - 2019-10-28 11:58 +0100
    Re: short float Dave Brower <dbrower@gmail.com> - 2020-12-09 11:21 -0800
      Re: short float Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2020-12-09 13:09 -0800
      Re: short float Philipp Klaus Krause <pkk@spth.de> - 2020-12-12 14:49 +0100
        Re: short float jacob navia <jacob@jacob.remcomp.fr> - 2020-12-13 13:42 +0100

#6006 — short float

FromPhilipp Klaus Krause <pkk@spth.de>
Date2019-10-28 11:58 +0100
Subjectshort float
Message-ID<qp6hju$j8h$1@solani.org>
While the idea of a short float was viewed favorably by the comitee a
few years ago, in London, the authors never followed up with a detailed
proposal.

I'd like to see short float in C, not just because a lot of hardware
supports it, but also as a relatively efficient floating-point type for
devices that don't have hardware support for floating-point at all:

http://www.colecovision.eu/stuff/proposal-short-float.html

[toc] | [next] | [standalone]


#6193

FromDave Brower <dbrower@gmail.com>
Date2020-12-09 11:21 -0800
Message-ID<f2a469ce-1ad3-43a9-ae0c-4f5fdd20478fn@googlegroups.com>
In reply to#6006
On Monday, October 28, 2019 at 3:58:08 AM UTC-7, Philipp Klaus Krause wrote:
> While the idea of a short float was viewed favorably by the comitee a 
> few years ago, in London, the authors never followed up with a detailed 
> proposal. 
> 
> I'd like to see short float in C, not just because a lot of hardware 
> supports it, but also as a relatively efficient floating-point type for 
> devices that don't have hardware support for floating-point at all: 
> 
> http://www.colecovision.eu/stuff/proposal-short-float.html

Just stumbled on this.   If there are OpenGL unsigned floats, why not have  'unsigned short float' as a thing, with 'short float' as a signed type?

(Yes, I know it's a year later).

-dB

[toc] | [prev] | [next] | [standalone]


#6194

FromKeith Thompson <Keith.S.Thompson+u@gmail.com>
Date2020-12-09 13:09 -0800
Message-ID<87eejyeleo.fsf@nosuchdomain.example.com>
In reply to#6193
Dave Brower <dbrower@gmail.com> writes:
> On Monday, October 28, 2019 at 3:58:08 AM UTC-7, Philipp Klaus Krause wrote:
>> While the idea of a short float was viewed favorably by the comitee a 
>> few years ago, in London, the authors never followed up with a detailed 
>> proposal. 
>> 
>> I'd like to see short float in C, not just because a lot of hardware 
>> supports it, but also as a relatively efficient floating-point type for 
>> devices that don't have hardware support for floating-point at all: 
>> 
>> http://www.colecovision.eu/stuff/proposal-short-float.html
>
> Just stumbled on this.  If there are OpenGL unsigned floats, why not
> have 'unsigned short float' as a thing, with 'short float' as a signed
> type?
>
> (Yes, I know it's a year later).

This:
    https://www.khronos.org/opengl/wiki/Data_Type_(GLSL)
does not indicate that OpenGL has unsigned floats.

I found a reference to 10- and 11-bit unsigned floating-point types, but
I get the impression that they're not language-defined types.
    https://www.oreilly.com/library/view/opengl-programming-guide/9780132748445/app07lev1sec3.html
C would not be able to support a type whose size is not a multiple of
CHAR_BIT (bit fields notwithstanding).

-- 
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Working, but not speaking, for Philips Healthcare
void Void(void) { Void(); } /* The recursive call of the void */

[toc] | [prev] | [next] | [standalone]


#6195

FromPhilipp Klaus Krause <pkk@spth.de>
Date2020-12-12 14:49 +0100
Message-ID<rr2hpr$hs4$1@solani.org>
In reply to#6193
The proposal is dead anyway. Many, including Nvidia, now see float,
double and long double as mistakes that can't be undone, but shouldn't
be repeated either.
They'd prefer all floating-point formats to be defined precisely down to
the last bit in representation and semantics.

Philipp

[toc] | [prev] | [next] | [standalone]


#6196

Fromjacob navia <jacob@jacob.remcomp.fr>
Date2020-12-13 13:42 +0100
Message-ID<rr527p$pr2$1@gioia.aioe.org>
In reply to#6195
Le 12/12/2020 à 14:49, Philipp Klaus Krause a écrit :
> The proposal is dead anyway. Many, including Nvidia, now see float,
> double and long double as mistakes that can't be undone, but shouldn't
> be repeated either.
> They'd prefer all floating-point formats to be defined precisely down to
> the last bit in representation and semantics.
> 
> Philipp
> 

IEEE754 is dead also?

Can you point me to some written text by a comptetent authority that 
says what you are saying?

Thanks

[toc] | [prev] | [standalone]


Back to top | Article view | comp.std.c


csiph-web