public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/101508] [9/10/11/12 Regression] Possible undefined behaviour in cpp program using "unsigned" type starting with r9-4145 Date: Mon, 19 Jul 2021 10:46:42 +0000 [thread overview] Message-ID: <bug-101508-4-TQFcfpU0MQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101508-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101508 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |amker at gcc dot gnu.org Status|UNCONFIRMED |NEW Last reconfirmed| |2021-07-19 Summary|Possible undefined |[9/10/11/12 Regression] |behaviour in cpp program |Possible undefined |using "unsigned" type |behaviour in cpp program |starting from GCC 9 |using "unsigned" type | |starting with r9-4145 Target Milestone|--- |9.5 Ever confirmed|0 |1 --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Started with r9-4145-ga81e2c6240655f60a49c16e0d8bbfd2ba40bba51 Simplified C testcase: int main () { unsigned i; for (i = 0; i < 3; ++i) { if (i > i * 2) __builtin_abort (); } return 0; }
next prev parent reply other threads:[~2021-07-19 10:46 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-19 10:25 [Bug tree-optimization/101508] New: Possible undefined behaviour in cpp program using "unsigned" type starting from GCC 9 pnarsing at mathworks dot com 2021-07-19 10:46 ` jakub at gcc dot gnu.org [this message] 2021-07-19 11:00 ` [Bug tree-optimization/101508] [9/10/11/12 Regression] Possible undefined behaviour in cpp program using "unsigned" type starting with r9-4145 rguenth at gcc dot gnu.org 2022-01-17 14:02 ` rguenth at gcc dot gnu.org 2022-01-24 12:15 ` cvs-commit at gcc dot gnu.org 2022-01-24 12:44 ` [Bug tree-optimization/101508] [9/10/11 " rguenth at gcc dot gnu.org 2022-01-24 12:46 ` rguenth 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-101508-4-TQFcfpU0MQ@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).