public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/11475] support for printing/reading decimal numbers (_Decimal64)
Date: Mon, 30 Jun 2014 18:18:00 -0000	[thread overview]
Message-ID: <bug-11475-131-FCrM5jM3hK@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-11475-131@http.sourceware.org/bugzilla/>

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.


       reply	other threads:[~2014-06-30 18:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-11475-131@http.sourceware.org/bugzilla/>
2014-06-30 18:18 ` fweimer at redhat dot com [this message]
2010-04-07  8:40 [Bug libc/11475] New: " zimmerma+gcc at loria dot fr
2010-04-07  9:11 ` [Bug libc/11475] " vincent+libc at vinc17 dot org
2010-04-07  9:12 ` vincent+libc at vinc17 dot org
2010-04-07  9:16 ` zimmerma+gcc at loria dot fr
2010-04-07  9:17 ` vincent+libc at vinc17 dot org
2010-04-07  9:25 ` vincent+libc at vinc17 dot org
2010-04-07  9:38 ` schwab at linux-m68k dot org
2010-04-07 13:30 ` drepper at redhat dot com
2010-04-07 15:30 ` vincent+libc at vinc17 dot org
2010-04-28  8:15 ` zimmerma+gcc at loria dot fr

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=bug-11475-131-FCrM5jM3hK@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).