public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/111231] [12/13/14 regression] armhf: Miscompilation with -O2/-fno-exceptions level (-fno-tree-vectorize is working) Date: Tue, 16 Apr 2024 06:57:14 +0000 [thread overview] Message-ID: <bug-111231-4-sQEFti3cIV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111231-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111231 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=93946 --- Comment #33 from Richard Biener <rguenth at gcc dot gnu.org> --- Ah, there's now the commoned mems_same_for_tbaa_p. And indeed postreload triggers on the cselib.cc instance. But there we only have (gdb) p debug_rtx (src_equiv) (mem/c:SI (value:SI 90:4664 @0x421eba8/0x42e10c0) [1 MEM[(struct Vec128 *)_179]+12 S4 A32]) and in the loc list elt the setting_insn (insn 89 88 93 14 (parallel [ (set (mem/c:SI (reg/f:SI 12 ip [201]) [1 MEM[(struct Vec128 *)_179]+0 S4 A64]) (reg:SI 0 r0)) (set (mem/c:SI (plus:SI (reg/f:SI 12 ip [201]) (const_int 4 [0x4])) [1 MEM[(struct Vec128 *)_179]+4 S4 A32]) (reg:SI 1 r1)) (set (mem/c:SI (plus:SI (reg/f:SI 12 ip [201]) (const_int 8 [0x8])) [1 MEM[(struct Vec128 *)_179]+8 S4 A64]) (reg:SI 2 r2)) (set (mem/c:SI (plus:SI (reg/f:SI 12 ip [201]) (const_int 12 [0xc])) [1 MEM[(struct Vec128 *)_179]+12 S4 A32]) (reg:SI 3 r3)) ]) 435 {*stm4_} (nil)) cselib_redundant_set_p isn't a good API to alter an earlier SET but it might be adjusted to return it so postreload could pass in an optional output parameter which when present would relax the alias check and return the earlier SET for further consideration / altering. Hoping CSELIB tables will be unaffected by altering that insn.
next prev parent reply other threads:[~2024-04-16 6:57 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-30 6:47 [Bug target/111231] New: armhf: Miscompilation at O2 level malat at debian dot org 2023-08-30 6:49 ` [Bug target/111231] " malat at debian dot org 2023-08-30 6:51 ` malat at debian dot org 2023-08-30 7:18 ` [Bug target/111231] armhf: Miscompilation at O2 level (O1 is working) malat at debian dot org 2023-08-31 6:49 ` malat at debian dot org 2023-09-05 16:24 ` malat at debian dot org 2023-09-14 13:52 ` [Bug target/111231] [13/14 Regression] " malat at debian dot org 2023-09-15 8:06 ` [Bug target/111231] armhf: Miscompilation with -O2/-fno-exceptions level (-O2 " malat at debian dot org 2023-09-26 6:29 ` malat at debian dot org 2023-09-26 6:29 ` malat at debian dot org 2023-09-26 6:31 ` malat at debian dot org 2023-09-26 6:32 ` malat at debian dot org 2023-09-26 9:00 ` xry111 at gcc dot gnu.org 2023-10-06 6:16 ` [Bug target/111231] armhf: Miscompilation with -O2/-fno-exceptions level (-fno-tree-vectorize " malat at debian dot org 2023-10-06 6:21 ` malat at debian dot org 2023-10-06 6:47 ` malat at debian dot org 2023-12-15 7:33 ` malat at debian dot org 2024-03-17 2:44 ` [Bug target/111231] [12/13/14 regression] " sjames at gcc dot gnu.org 2024-03-17 2:46 ` sjames at gcc dot gnu.org 2024-03-22 13:39 ` law at gcc dot gnu.org 2024-03-22 18:02 ` rearnsha at gcc dot gnu.org 2024-03-25 12:46 ` rguenth at gcc dot gnu.org 2024-04-11 14:13 ` rearnsha at gcc dot gnu.org 2024-04-11 14:28 ` rearnsha at gcc dot gnu.org 2024-04-11 14:29 ` rearnsha at gcc dot gnu.org 2024-04-11 14:41 ` rearnsha at gcc dot gnu.org 2024-04-11 18:25 ` pinskia at gcc dot gnu.org 2024-04-12 6:17 ` rguenth at gcc dot gnu.org 2024-04-12 10:08 ` rearnsha at gcc dot gnu.org 2024-04-12 10:40 ` rearnsha at gcc dot gnu.org 2024-04-12 10:51 ` rguenth at gcc dot gnu.org 2024-04-12 13:10 ` rearnsha at gcc dot gnu.org 2024-04-15 6:46 ` rguenth at gcc dot gnu.org 2024-04-15 14:47 ` rearnsha at gcc dot gnu.org 2024-04-16 6:46 ` rguenth at gcc dot gnu.org 2024-04-16 6:57 ` rguenth at gcc dot gnu.org [this message] 2024-04-16 9:59 ` rearnsha at gcc dot gnu.org 2024-04-16 10:34 ` rguenther at suse dot de
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-111231-4-sQEFti3cIV@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).