public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: axiong@ca.ibm.com
To: gcc-gnats@gcc.gnu.org
Subject: libstdc++/9548: 64-bit copiling/linking: incorrect results from setf(ios::fixed) or precision(-1)
Date: Mon, 03 Feb 2003 18:16:00 -0000	[thread overview]
Message-ID: <20030203180720.9892.qmail@sources.redhat.com> (raw)


>Number:         9548
>Category:       libstdc++
>Synopsis:       64-bit copiling/linking: incorrect results from setf(ios::fixed) or precision(-1)
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Feb 03 18:16:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Guan-Zhu (Andrew) Xiong
>Release:        gcc version 3.2
>Organization:
>Environment:
Linux Version 2.4.19
SuSE SLES 8 (ppc) - Kernel 2.4.19-ul1-ppc64-SMP (31)
>Description:
=> for 64-bit g++ compiling/linking: 
   "cout.setf(ios::fixed); cout.precision (-1);" 
   does not work as expected.

=> For the given C++ code, after 64-bit g++ compiling,
   if you run it then you will get output:
   -----------------
   Output 30.5 as: 30

   The correct output should be: 
   -----------------
   Output 30.5 as: 30.500000

=> Refenece: ISO C++ standard
   The value passed to precision(int i) must be greater 
   than zero. If the value is negative the floating point
   insertion operators will use the default value 
   which is 6.
>How-To-Repeat:
1) Compile the given code with "g++ 64-bit compiler"
   - e.g., /opt/cross/bin/powerpc64-linux-g++ -o hello x.C
2) Run it - hello
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2003-02-03 18:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-03 18:16 axiong [this message]
2003-02-03 18:26 axiong
2003-02-03 23:41 paolo

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=20030203180720.9892.qmail@sources.redhat.com \
    --to=axiong@ca.ibm.com \
    --cc=gcc-gnats@gcc.gnu.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).