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 tree-optimization/102622] [9/10/12 Regression] Wrong code with -O1 and above due to phiopt and signed one bit integer types Date: Sun, 10 Oct 2021 01:05:09 +0000 [thread overview] Message-ID: <bug-102622-4-sPM6aDU7BF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102622-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102622 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|12.0 |9.5 Known to work|9.3.0 |11.1.0, 4.9.2, 7.1.0, 8.5.0 Known to fail| |10.3.0, 9.1.0, 9.4.0 Summary|[12 Regression] Wrong code |[9/10/12 Regression] Wrong |with -O3 for skylake-avx512 |code with -O1 and above due |and icelake-server by |to phiopt and signed one |r12-3903 |bit integer types --- Comment #17 from Andrew Pinski <pinskia at gcc dot gnu.org> --- So the reason why we didn't hit it in GCC 11 (and before) was the order of the following was swapped in phiopt compared to what it is in match.pd now: a ? -1 : 0 -> -a a ? powerof2cst : 0 -> a << (log2(powerof2cst)) That is did the powerof2cst case before it did the -1 case. I am going to test that to see if it works here which I think it does. In fact my new testcase fails in GCC 9.1.0-10.3.0 :). I am going to fix this for the trunk and come up with a fix for the other branches later on. And yes the regression markers are a bit off right now but that is because the bug is not latent on the 12 branch.
next prev parent reply other threads:[~2021-10-10 1:05 UTC|newest] Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-05 19:37 [Bug tree-optimization/102622] New: Wrong code with -O3 for skylake-avx512 and icelake-server vsevolod.livinskij at frtk dot ru 2021-10-05 22:21 ` [Bug tree-optimization/102622] [12 Regression] " pinskia at gcc dot gnu.org 2021-10-05 22:36 ` pinskia at gcc dot gnu.org 2021-10-05 23:31 ` pinskia at gcc dot gnu.org 2021-10-06 7:23 ` [Bug tree-optimization/102622] [12 Regression] Wrong code with -O3 for skylake-avx512 and icelake-server by r12-3903 aldyh at gcc dot gnu.org 2021-10-06 8:42 ` rguenth at gcc dot gnu.org 2021-10-06 12:55 ` hjl.tools at gmail dot com 2021-10-06 13:04 ` hjl.tools at gmail dot com 2021-10-06 13:10 ` aldyh at gcc dot gnu.org 2021-10-06 13:12 ` aldyh at gcc dot gnu.org 2021-10-06 13:26 ` hjl.tools at gmail dot com 2021-10-06 14:19 ` aldyh at redhat dot com 2021-10-06 14:21 ` hjl.tools at gmail dot com 2021-10-07 16:07 ` aldyh at gcc dot gnu.org 2021-10-07 21:29 ` pinskia at gcc dot gnu.org 2021-10-07 21:31 ` pinskia at gcc dot gnu.org 2021-10-08 6:04 ` pinskia at gcc dot gnu.org 2021-10-09 22:25 ` pinskia at gcc dot gnu.org 2021-10-10 1:05 ` pinskia at gcc dot gnu.org [this message] 2021-10-10 1:54 ` [Bug tree-optimization/102622] [9/10/12 Regression] Wrong code with -O1 and above due to phiopt and signed one bit integer types pinskia at gcc dot gnu.org 2021-10-10 5:49 ` pinskia at gcc dot gnu.org 2021-10-10 9:04 ` cvs-commit at gcc dot gnu.org 2021-10-10 9:06 ` [Bug tree-optimization/102622] [9/10 " pinskia at gcc dot gnu.org 2021-10-10 9:18 ` pinskia at gcc dot gnu.org 2021-10-10 23:21 ` pinskia at gcc dot gnu.org 2021-10-11 9:22 ` cvs-commit at gcc dot gnu.org 2021-10-11 9:24 ` [Bug tree-optimization/102622] [9 " pinskia at gcc dot gnu.org 2021-10-11 21:07 ` cvs-commit at gcc dot gnu.org 2021-10-11 21:08 ` pinskia at gcc dot gnu.org 2021-10-11 21:19 ` cvs-commit at gcc dot gnu.org 2021-11-09 19:03 ` cvs-commit 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-102622-4-sPM6aDU7BF@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).