public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/64054] 27_io/basic_ostream/inserters_arithmetic/char/hexfloat.cc FAILs
Date: Tue, 25 Nov 2014 15:20:00 -0000	[thread overview]
Message-ID: <bug-64054-4-GgxgQuVLbL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64054-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64054

--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Thanks - so it looks as though the problem is in std::stod which is pretty
simple, and can be reduced to:

#include <errno.h>
#include <stdio.h>
#include <stdlib.h>

int main()
{
      double d;

      char* endptr;
      errno = 0;
      const char* str = "0x1.1000000000000p+8";
      const double tmp = strtod(str, &endptr);

      if (endptr == str) {
        puts("no characters consumed");
    return 1;
      }
      else if (errno == ERANGE) {
        puts("ERANGE");
    return 2;
      }
      else if (*endptr) {
        printf("stopped at '%c'\n", *endptr);
        return 3;
      }
      else
    d = tmp;

     printf("%f %a\n", d, d);
}

Maybe Solaris' strtod() doesn't support hex floats in C++ code, so it will
print "stopped at 'x'"


  parent reply	other threads:[~2014-11-25 15:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-24 14:59 [Bug libstdc++/64054] New: " ro at gcc dot gnu.org
2014-11-24 14:59 ` [Bug libstdc++/64054] " ro at gcc dot gnu.org
2014-11-24 16:19 ` redi at gcc dot gnu.org
2014-11-24 16:48 ` schwab@linux-m68k.org
2014-11-24 17:24 ` redi at gcc dot gnu.org
2014-11-25 15:20 ` redi at gcc dot gnu.org [this message]
2014-11-25 15:42 ` ro at CeBiTec dot Uni-Bielefeld.DE
2014-11-25 16:11 ` redi at gcc dot gnu.org
2014-11-25 16:15 ` ro at CeBiTec dot Uni-Bielefeld.DE
2014-11-25 16:16 ` redi at gcc dot gnu.org
2014-11-26 13:40 ` ro at gcc dot gnu.org
2014-12-12 22:46 ` redi at gcc dot gnu.org
2014-12-15  9:44 ` ro at CeBiTec dot Uni-Bielefeld.DE
2015-04-22 12:01 ` jakub at gcc dot gnu.org
2015-07-16  9:20 ` rguenth at gcc dot gnu.org

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-64054-4-GgxgQuVLbL@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).