public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mhillen at linux dot ibm.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/92294] alias attribute generates incorrect code Date: Fri, 13 Nov 2020 09:30:24 +0000 [thread overview] Message-ID: <bug-92294-4-uhru9wvING@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-92294-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92294 --- Comment #6 from Marius Hillenbrand <mhillen at linux dot ibm.com> --- Same behavior on s390x: the testcase always calls abort(). As on aarch64, -fno-section-anchors avoids the issue. the first cse pass already makes a mistake -- on both aarch64 and s390x, the compare looses its memory-read for the current value of b and instead reuses the constant 1 assigned to b earlier. on aarch64 that looks like (insn # # # 2 (set (reg:SI 110) (mem:SI (plus:DI (mult:DI (reg:DI 109) (const_int 4 [0x4])) (reg/f:DI 107)) [1 b[off.0_1]+0 S4 A32])) "alias-2.c":9:6# {*movsi_aarch64} (nil)) (insn # # # 2 (set (reg:CC 66 cc) (compare:CC (reg:SI 110) (const_int 2 [0x2]))) "alias-2.c":9:6# {cmpsi} (nil)) ... becomes ... (insn # # # 2 (set (reg:SI 100) (const_int 1 [0x1])) "alias-2.c":7:9# {*movsi_aarch64} (nil)) [from the write to b] ... (insn # # # 2 (set (reg:CC 66 cc) (compare:CC (reg:SI 100) (const_int 2 [0x2]))) "alias-2.c":9:6# {cmpsi} (expr_list:REG_DEAD (reg:SI 110 [ b[off.0_1] ]) (nil)))
next prev parent reply other threads:[~2020-11-13 9:30 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-92294-4@http.gcc.gnu.org/bugzilla/> 2020-05-07 11:56 ` jakub at gcc dot gnu.org 2020-07-23 6:51 ` rguenth at gcc dot gnu.org 2020-11-13 9:30 ` mhillen at linux dot ibm.com [this message] 2020-11-19 11:03 ` mhillen at linux dot ibm.com 2020-11-19 13:02 ` mhillen at linux dot ibm.com 2020-11-23 20:49 ` rsandifo at gcc dot gnu.org 2021-01-19 17:51 ` cvs-commit at gcc dot gnu.org 2021-01-19 17:53 ` rsandifo at gcc dot gnu.org 2022-02-11 9:13 ` pinskia 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-92294-4-uhru9wvING@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).