This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libc/11475] support for printing/reading decimal numbers (_Decimal64)


https://sourceware.org/bugzilla/show_bug.cgi?id=11475

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|                            |security-

--- Comment #9 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
Subject: Re:  support for printing/reading decimal numbers
 (_Decimal64)

On Wed, 28 Apr 2010, zimmerma+gcc at loria dot fr wrote:

> ------- Additional Comments From zimmerma+gcc at loria dot fr  2010-04-28 08:15 -------
> (In reply to comment #6)
> > This is what the printf hooks are for.  I'm not going to add any such
> > non-standard conversion.  It far too dangerous a compability risk going forward.
> 
> Dear Ulrich, please can you explain why this is "non-standard". With respect to
> which standard? Is _Decimal64 standard?

A Technical Report Type 2 (such as TR 24732) is not a standard or an 
amendment to a standard.

> Also, if someone provides changes to scanf/printf based on functions already
> existing in libbid or libdecnumber (currently used internally by gcc) for
> conversions between strings and decimal formats, would them be included in glibc?

The functionality is in the libfdp add-on.  This is an example of what the 
add-on mechanism is for; it doesn't need to be in the core libc.  (I 
imagine the libdfp people will propose a scanf hook facility at some point 
to allow that part to be fully implemented in an add-on.  One remaining 
DFP requirement relates to the predefined macro __STDC_DEC_FP__ but 
unfortunately my proposal for a change which would also allow that to be 
handled entirely within the add-on has stalled; see bug 10110.)



-- 
You are receiving this mail because:
You are on the CC list for the bug.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]