public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sebastien.michelland@ens-lyon.fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/106609] [SH] miscompilation of loop involving noreturn call Date: Mon, 15 Aug 2022 09:47:06 +0000 [thread overview] Message-ID: <bug-106609-4-a4mSrzS5IJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106609-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106609 --- Comment #2 from Sébastien Michelland <sebastien.michelland@ens-lyon.fr> --- Yes there are delay slots for all branches except bt and bf, so here bt.s, jsr and rts all have one. (-fno-delayed-branches avoids them but that doesn't affect the bad optimization in this case.) Adding -fno-schedule-insns -fno-schedule-insns2 doesn't help; the test and load are still eliminated. In fact, I negated the entirety of -Q --help=optimizers and still got an incorrect output. It seems that the problem lies further downstream. I dumped various RTL stages and -fdump-rtl-mach is the first stage where the comparison to 0 is gone, if the order in the manual is anything to go by. Since I have both functional and non-functional outputs from different RTL stages, I'm switching the component to rtl-optimization.
next prev parent reply other threads:[~2022-08-15 9:47 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-13 17:31 [Bug c/106609] New: " sebastien.michelland@ens-lyon.fr 2022-08-15 8:28 ` [Bug middle-end/106609] " rguenth at gcc dot gnu.org 2022-08-15 9:47 ` sebastien.michelland@ens-lyon.fr [this message] 2022-08-15 15:52 ` [Bug target/106609] " pinskia at gcc dot gnu.org 2022-08-16 21:03 ` [Bug target/106609] [SH] miscompilation due to incorrect elimination of comparisons to 0 sebastien.michelland@ens-lyon.fr 2022-08-16 21:03 ` sebastien.michelland@ens-lyon.fr 2022-08-17 8:09 ` sebastien.michelland@ens-lyon.fr 2022-11-24 13:13 ` [Bug target/106609] [12/13 Regression] sh3eb-elf cross compiler is being miscompiled since r12-1525-g3155d51bfd1de8b6c4645 jakub at gcc dot gnu.org 2022-11-24 14:38 ` [Bug target/106609] [12 " jakub at gcc dot gnu.org 2022-11-24 17:04 ` sebastien.michelland@ens-lyon.fr 2023-02-28 23:08 ` sam at gentoo dot org 2023-05-08 12:25 ` 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-106609-4-a4mSrzS5IJ@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).