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/101254] [12 Regression] gcc head does not comply fully to -fwrapv since r12-1723 Date: Tue, 29 Jun 2021 09:34:36 +0000 [thread overview] Message-ID: <bug-101254-4-8y02CR2wWj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101254-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101254 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|gcc head does not comply |[12 Regression] gcc head |fully to -fwrapv |does not comply fully to | |-fwrapv since r12-1723 CC| |aldyh at gcc dot gnu.org, | |amacleod at redhat dot com, | |jakub at gcc dot gnu.org Status|UNCONFIRMED |NEW Last reconfirmed| |2021-06-29 Component|c |tree-optimization Target Milestone|--- |12.0 Ever confirmed|0 |1 --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Started with r12-1723-gae6b830f31a47aca7ca24c4fea245c29214eef3a Adjusted testcase for testsuite: /* PR tree-optimization/101254 */ /* { dg-do run } */ /* { dg-options "-O2 -fwrapv" } */ int foo (long long imin, long long imax) { if (imin > imax) return 0; else if (imax - imin < 0 || (imax - imin) + 1 < 0) return 0; return 1; } int main () { long long imax = __LONG_LONG_MAX__; long long imin = -imax - 1; if (!foo (-10, 10)) __builtin_abort (); if (foo (-10, imax)) __builtin_abort (); if (foo (imin, imax)) __builtin_abort (); return 0; }
next prev parent reply other threads:[~2021-06-29 9:34 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-29 9:19 [Bug c/101254] New: gcc head does not comply fully to -fwrapv bugzilla.gnu at coelho dot net 2021-06-29 9:34 ` jakub at gcc dot gnu.org [this message] 2021-06-29 12:07 ` [Bug tree-optimization/101254] [12 Regression] gcc head does not comply fully to -fwrapv since r12-1723 rguenth at gcc dot gnu.org 2021-06-29 15:09 ` amacleod at redhat dot com 2021-06-29 15:21 ` jakub at gcc dot gnu.org 2021-06-29 15:25 ` jakub at gcc dot gnu.org 2021-06-29 15:42 ` amacleod at redhat dot com 2021-06-29 15:47 ` jakub at gcc dot gnu.org 2021-06-29 15:48 ` jakub at gcc dot gnu.org 2021-06-29 15:55 ` amacleod at redhat dot com 2021-06-29 17:11 ` amacleod at redhat dot com 2021-06-29 17:38 ` jakub at gcc dot gnu.org 2021-06-29 18:27 ` amacleod at redhat dot com 2021-06-29 19:09 ` cvs-commit at gcc dot gnu.org 2021-06-29 19:10 ` amacleod at redhat dot com
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-101254-4-8y02CR2wWj@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).