public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105774] Bogus overflow in constant expression with signed char++ Date: Sat, 22 Oct 2022 20:55:56 +0000 [thread overview] Message-ID: <bug-105774-4-sZ1P0ppSZC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105774-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105774 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Bogus overflow in constant |Bogus overflow in constant |expression with char++ |expression with signed | |char++ Known to fail| |5.1.0 --- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Here is a C++14 testcase (lambdas were not constexpr in C++14) which shows the issue has been there since GCC 5 (which didn't have C++17 support): constexpr signed char f(void){ signed char x = 127; return ++x; } int main() { constexpr auto _ = f(); }
next prev parent reply other threads:[~2022-10-22 20:55 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-30 14:31 [Bug c++/105774] New: Bogus overflow in constant expression jeff at jgarrett dot org 2022-05-30 14:39 ` [Bug c++/105774] " klaus.doldinger64 at googlemail dot com 2022-06-01 11:40 ` rguenth at gcc dot gnu.org 2022-10-22 20:55 ` pinskia at gcc dot gnu.org [this message] 2022-10-22 20:56 ` [Bug c++/105774] Bogus overflow in constant expression with signed char++ pinskia at gcc dot gnu.org 2022-10-23 16:46 ` jakub at gcc dot gnu.org 2022-10-24 14:26 ` cvs-commit at gcc dot gnu.org 2022-10-25 9:05 ` jakub at gcc dot gnu.org 2022-11-03 0:23 ` cvs-commit at gcc dot gnu.org 2022-11-04 8:31 ` cvs-commit at gcc dot gnu.org 2023-05-03 15:19 ` cvs-commit at gcc dot gnu.org 2023-05-04 7:17 ` 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-105774-4-sZ1P0ppSZC@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).