public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "avieira at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/104498] Alias attribute being ignored by scheduler Date: Fri, 11 Feb 2022 11:52:06 +0000 [thread overview] Message-ID: <bug-104498-4-WfMddeZ43M@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104498-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104498 --- Comment #3 from avieira at gcc dot gnu.org --- Sorry some confusion there, I thought it was base_alias_check bailing out early, but that seems to return true, it is the memrefs_conflict_p that returns 0. I suspect rtx_equal_for_memref_p should have returned 1 for: x: (plus:DI (mult:DI (reg:DI 99 [ off.0_1 ]) (const_int 4 [0x4])) (const:DI (plus:DI (symbol_ref:DI ("*.LANCHOR0") [flags 0x182]) (const_int 16 [0x10])))) and y: (plus:DI (mult:DI (reg:DI 99 [ off.0_1 ]) (const_int 4 [0x4])) (symbol_ref:DI ("b") [flags 0x2] <var_decl 0xfffff7635f30 b>)) But it does not... must be because of that trailing (equivalence notes? that's what I assume they are?)
next prev parent reply other threads:[~2022-02-11 11:52 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-11 9:25 [Bug rtl-optimization/104498] New: " avieira at gcc dot gnu.org 2022-02-11 9:26 ` [Bug rtl-optimization/104498] " avieira at gcc dot gnu.org 2022-02-11 10:27 ` rguenth at gcc dot gnu.org 2022-02-11 11:52 ` avieira at gcc dot gnu.org [this message] 2022-02-11 12:10 ` rguenth at gcc dot gnu.org 2022-02-11 12:50 ` avieira at gcc dot gnu.org 2022-02-11 13:21 ` rsandifo at gcc dot gnu.org 2022-02-11 13:56 ` avieira at gcc dot gnu.org 2022-02-11 14:31 ` rsandifo at gcc dot gnu.org 2022-02-21 9:45 ` cvs-commit at gcc dot gnu.org 2022-02-21 11:39 ` avieira 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-104498-4-WfMddeZ43M@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).