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/98028] [8/9/10/11 Regression] __builtin_sub_overflow_p not folded to const when some constraints are known Date: Fri, 27 Nov 2020 11:12:08 +0000 [thread overview] Message-ID: <bug-98028-4-L9K2XIVeXG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98028-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98028 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|__builtin_sub_overflow_p |[8/9/10/11 Regression] |not folded to const when |__builtin_sub_overflow_p |some constraints are known |not folded to const when | |some constraints are known Last reconfirmed| |2020-11-27 Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Target Milestone|--- |8.5 CC| |amacleod at redhat dot com, | |jakub at gcc dot gnu.org --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> --- f1 changed with r8-2630-g0db8ddfcb660397bab428ce0d271967d24c23177, until then dom propagated one of those SSA_NAMEs, so we ended up with __builtin_sub_overflow_p (i, i, (unsigned) 0) which we can still even on the trunk optimize. Anyway, I guess all this is a task for the symbolic value ranges in the ranger.
next prev parent reply other threads:[~2020-11-27 11:12 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-27 10:50 [Bug tree-optimization/98028] New: " denis.campredon at gmail dot com 2020-11-27 11:12 ` jakub at gcc dot gnu.org [this message] 2021-01-14 9:49 ` [Bug tree-optimization/98028] [8/9/10/11 Regression] " rguenth at gcc dot gnu.org 2021-01-14 14:23 ` amacleod at redhat dot com 2021-02-12 13:41 ` jakub at gcc dot gnu.org 2021-02-12 14:43 ` amacleod at redhat dot com 2021-05-14 9:54 ` [Bug tree-optimization/98028] [9/10/11/12 " jakub at gcc dot gnu.org 2021-06-01 8:19 ` rguenth at gcc dot gnu.org 2022-05-27 9:44 ` [Bug tree-optimization/98028] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:42 ` jakub at gcc dot gnu.org 2023-07-07 10:38 ` [Bug tree-optimization/98028] [11/12/13/14 " 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-98028-4-L9K2XIVeXG@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).