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/103226] [12 Regression] Recent change to copy-headers causes execution failure for gcc.dg/torture/pr80974 Date: Sat, 20 Nov 2021 07:10:55 +0000 [thread overview] Message-ID: <bug-103226-4-TzUl7qwAtl@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103226-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103226 Jeffrey A. Law <law at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P1 |P4 --- Comment #20 from Jeffrey A. Law <law at gcc dot gnu.org> --- Your c#19 was a bit hard to follow. But you hit the key issue. Namely that the doloop pattern will set/clobber the condition codes if it gets split. Failure to show that clobber means that IRA/LRA have incorrect dataflow and make incorrect decisions. I'm testing the obvious fix of adding the clobber. It may be possible to improve on my patch, but I'll leave that to someone who really cares about the port.
next prev parent reply other threads:[~2021-11-20 7:10 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-13 20:39 [Bug tree-optimization/103226] New: " law at gcc dot gnu.org 2021-11-14 10:59 ` [Bug tree-optimization/103226] " aldyh at gcc dot gnu.org 2021-11-15 9:03 ` rguenth at gcc dot gnu.org 2021-11-16 2:30 ` law at gcc dot gnu.org 2021-11-17 11:14 ` aldyh at gcc dot gnu.org 2021-11-17 11:32 ` aldyh at gcc dot gnu.org 2021-11-17 15:00 ` tnfchris at gcc dot gnu.org 2021-11-17 15:02 ` tnfchris at gcc dot gnu.org 2021-11-17 15:53 ` aldyh at gcc dot gnu.org 2021-11-17 16:09 ` tnfchris at gcc dot gnu.org 2021-11-17 16:28 ` law at gcc dot gnu.org 2021-11-17 16:29 ` law at gcc dot gnu.org 2021-11-17 16:31 ` aldyh at gcc dot gnu.org 2021-11-17 17:18 ` aldyh at gcc dot gnu.org 2021-11-17 17:54 ` tnfchris at gcc dot gnu.org 2021-11-17 18:31 ` law at gcc dot gnu.org 2021-11-17 18:43 ` aldyh at gcc dot gnu.org 2021-11-17 19:26 ` aldyh at gcc dot gnu.org 2021-11-17 20:02 ` aldyh at gcc dot gnu.org 2021-11-18 13:28 ` aldyh at gcc dot gnu.org 2021-11-20 7:10 ` law at gcc dot gnu.org [this message] 2021-11-20 7:23 ` aldyh at gcc dot gnu.org 2021-11-20 16:30 ` cvs-commit at gcc dot gnu.org 2021-11-20 16:31 ` law at gcc dot gnu.org 2021-12-02 14:55 ` hp 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-103226-4-TzUl7qwAtl@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).