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++/97798] FTB msp430-elf error: the value of '__gnu_cxx::__numeric_traits_integer<__int20>::__max' is not usable in a constant expression Date: Thu, 12 Nov 2020 12:13:50 +0000 [thread overview] Message-ID: <bug-97798-4-od8lD79XEW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97798-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97798 --- Comment #11 from Jonathan Wakely <redi at gcc dot gnu.org> --- Fixed for gcc-11 but it should be backported too. Even if the compiler doesn't reject the overflow in the constant expressions, the values of the trait are still wrong for __int20.
next prev parent reply other threads:[~2020-11-12 12:13 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-11 13:55 [Bug c++/97798] New: " jozefl at gcc dot gnu.org 2020-11-11 14:38 ` [Bug c++/97798] " mpolacek at gcc dot gnu.org 2020-11-11 14:56 ` jozefl at gcc dot gnu.org 2020-11-11 15:26 ` mpolacek at gcc dot gnu.org 2020-11-11 15:51 ` mpolacek at gcc dot gnu.org 2020-11-11 18:37 ` mpolacek at gcc dot gnu.org 2020-11-12 0:03 ` redi at gcc dot gnu.org 2020-11-12 0:36 ` [Bug libstdc++/97798] " redi at gcc dot gnu.org 2020-11-12 0:38 ` redi at gcc dot gnu.org 2020-11-12 10:00 ` jozefl at gcc dot gnu.org 2020-11-12 12:11 ` cvs-commit at gcc dot gnu.org 2020-11-12 12:13 ` redi at gcc dot gnu.org [this message] 2020-11-12 12:30 ` jozefl at gcc dot gnu.org 2020-11-12 14:27 ` redi at gcc dot gnu.org 2020-11-12 16:06 ` jozefl at gcc dot gnu.org 2020-11-12 17:43 ` redi at gcc dot gnu.org 2020-11-12 19:31 ` jozefl at gcc dot gnu.org 2020-11-12 19:32 ` redi at gcc dot gnu.org 2020-11-13 13:24 ` redi at gcc dot gnu.org 2020-11-13 13:49 ` jozefl at gcc dot gnu.org 2020-11-13 14:52 ` cvs-commit at gcc dot gnu.org 2020-11-13 14:55 ` cvs-commit at gcc dot gnu.org 2020-11-13 14:57 ` redi at gcc dot gnu.org 2020-11-13 15:12 ` jozefl at gcc dot gnu.org 2020-11-13 15:30 ` redi 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-97798-4-od8lD79XEW@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).