From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-484613-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 21851 invoked by alias); 25 Apr 2015 10:25:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Received: (qmail 21827 invoked by uid 48); 25 Apr 2015 10:25:27 -0000
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
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 5.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: blocker
X-Bugzilla-Who: john at johnmaddock dot co.uk
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter
Message-ID: <bug-65883-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-04/txt/msg02165.txt.bz2

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.