public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "john at johnmaddock dot co.uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/65883] New: numeric_limits<unsigned __int128>::max() returns incorrect value
Date: Sat, 25 Apr 2015 10:25:00 -0000	[thread overview]
Message-ID: <bug-65883-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 65883
           Summary: numeric_limits<unsigned __int128>::max() returns
                    incorrect value
           Product: gcc
           Version: 5.1.0
            Status: UNCONFIRMED
          Severity: blocker
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: john at johnmaddock dot co.uk

std::numeric_limits<unsigned __int128>::max() returns
0x7fffffffffffffffffffffffffffffff which is definitely not 2^128-1.  Looks like
a cut and paste error from numeric_limits<__int128>?

This is on Xubuntu 64-bit.

This is a showstopper for Boost.Multiprecision which has asserts that are
incorrectly triggered by the bug.

Regards, John Maddock.


             reply	other threads:[~2015-04-25 10:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-25 10:25 john at johnmaddock dot co.uk [this message]
2015-04-25 10:38 ` [Bug libstdc++/65883] [5/6 Regression] " glisse at gcc dot gnu.org
2015-04-28 19:36 ` glisse at gcc dot gnu.org
2015-04-28 19:46 ` [Bug libstdc++/65883] [5 " glisse at gcc dot gnu.org
2015-05-04 18:20 ` jakub at gcc dot gnu.org
2015-05-04 18:30 ` jakub 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-65883-4@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).