public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/108273] Inconsistent dfa state between debug and non-debug Date: Thu, 23 Feb 2023 09:08:51 +0000 [thread overview] Message-ID: <bug-108273-4-FVgMVobxJf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108273-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108273 --- Comment #4 from Kewen Lin <linkw at gcc dot gnu.org> --- Starting from r13-5154-g733a1b777f16cd, this failure is gone on Power10 LE (or with explicit -mcpu=power10), but it shows up on Power8 LE. By checking r13-5154, this behavior change is expected, the priorities of some insns change due to that commit, it further affects the scheduling decision on which insn is scheduled ahead.
next prev parent reply other threads:[~2023-02-23 9:08 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-03 10:25 [Bug rtl-optimization/108273] New: " linkw at gcc dot gnu.org 2023-01-03 10:26 ` [Bug rtl-optimization/108273] " linkw at gcc dot gnu.org 2023-01-10 16:40 ` bergner at gcc dot gnu.org 2023-02-23 6:58 ` linkw at gcc dot gnu.org 2023-02-23 7:00 ` linkw at gcc dot gnu.org 2023-02-23 7:03 ` linkw at gcc dot gnu.org 2023-02-23 9:08 ` linkw at gcc dot gnu.org [this message] 2023-02-23 9:12 ` linkw at gcc dot gnu.org 2023-04-26 6:57 ` rguenth at gcc dot gnu.org 2023-07-27 9:24 ` rguenth at gcc dot gnu.org 2024-05-21 9:13 ` jakub 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-108273-4-FVgMVobxJf@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).