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

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

Marc Glisse <glisse at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2015-04-25
            Summary|numeric_limits<unsigned     |[5/6 Regression]
                   |__int128>::max() returns    |numeric_limits<unsigned
                   |incorrect value             |__int128>::max() returns
                   |                            |incorrect value
     Ever confirmed|0                           |1

--- Comment #1 from Marc Glisse <glisse at gcc dot gnu.org> ---
Indeed, the specialization for struct numeric_limits<unsigned TYPE> uses TYPE
instead of unsigned TYPE for max :-(


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

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