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 Regression] numeric_limits<unsigned __int128>::max() returns incorrect value Date: Tue, 28 Apr 2015 19:46:00 -0000 [thread overview] Message-ID: <bug-65883-4-Feu5Vwfo5y@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 ---------------------------------------------------------------------------- Keywords| |wrong-code Known to work| |4.9.2, 6.0 Target Milestone|--- |5.2 Summary|[5/6 Regression] |[5 Regression] |numeric_limits<unsigned |numeric_limits<unsigned |__int128>::max() returns |__int128>::max() returns |incorrect value |incorrect value Known to fail| |5.1.0 --- Comment #3 from Marc Glisse <glisse at gcc dot gnu.org> --- Fixed on trunk. This needs to be backported to 5, but I don't have time to do it right now, anyone feel free...
next prev parent reply other threads:[~2015-04-28 19:46 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 ` [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 ` glisse at gcc dot gnu.org [this message] 2015-05-04 18:20 ` [Bug libstdc++/65883] [5 " 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-Feu5Vwfo5y@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: linkBe 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).