public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/104987] [12 Regression] Recent change causing vrp13.c regressions on several targets Date: Sun, 27 Mar 2022 16:52:07 +0000 [thread overview] Message-ID: <bug-104987-4-Ms2ZAL4twi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104987-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104987 Jeffrey A. Law <law at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target|iq2000-elf, v850e-elf |iq2000-elf Priority|P3 |P4 --- Comment #8 from Jeffrey A. Law <law at gcc dot gnu.org> --- V850 simulator fix has been posted to the binutils list. I've never really hacked the iq2000, but from the looks of things I think it's mis-compiling mulsi3 in libgcc. In particular, I don't think it's handling delay slots properly for the bbi instruction. reorg has tagged it as a nullified-if-false branch, but it appears that we're using the wrong form at assembly time and the instruction in the delay slot always executes. So P4 as this appears to be an iq2000 specific issue.
next prev parent reply other threads:[~2022-03-27 16:52 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-19 18:12 [Bug tree-optimization/104987] New: " law at gcc dot gnu.org 2022-03-21 8:54 ` [Bug tree-optimization/104987] " rguenth at gcc dot gnu.org 2022-03-21 16:59 ` amacleod at redhat dot com 2022-03-21 17:16 ` law at gcc dot gnu.org 2022-03-21 21:16 ` amacleod at redhat dot com 2022-03-23 16:55 ` jakub at gcc dot gnu.org 2022-03-23 16:59 ` jakub at gcc dot gnu.org 2022-03-26 17:41 ` law at gcc dot gnu.org 2022-03-26 23:34 ` law at gcc dot gnu.org 2022-03-27 16:52 ` law at gcc dot gnu.org [this message] 2022-04-03 22:24 ` [Bug target/104987] " cvs-commit at gcc dot gnu.org 2022-04-03 22:26 ` law 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-104987-4-Ms2ZAL4twi@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).