public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/101188] [postreload] Uses content of a clobbered register Date: Sun, 28 May 2023 19:26:58 +0000 [thread overview] Message-ID: <bug-101188-4-xqYk7QQ2tC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101188-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101188 --- Comment #9 from Georg-Johann Lay <gjl at gcc dot gnu.org> --- The bug works as follows: postreload.cc::reload_cse_move2add() loops over all insns, and at some point it encounters (insn 44 14 15 2 (set (reg/f:HI 14 r14 [58]) (reg/v/f:HI 16 r16 [orig:51 self ] [51])) "fail1.c":28:5 101 {*movhi_split} (nil)) During the analysis for that insn, it executes rtx_insn *next = next_nonnote_nondebug_insn (insn); rtx set = NULL_RTX; if (next) set = single_set (next); where next is (insn 15 44 16 2 (parallel [ (set (reg/f:HI 14 r14 [58]) (plus:HI (reg/f:HI 14 r14 [58]) (const_int 68 [0x44]))) (clobber (reg:QI 31 r31)) ]) "fail1.c":28:5 175 {addhi3_clobber} (nil)) Further down, it continues with success = 0: if (success) delete_insn (insn); changed |= success; insn = next; [...] continue; The scan then continues with NEXT_INSN (insn), which is the insn AFTER insn 15, so the CLOBBER of QI:31 in insn 15 is bypassed, and note_stores or similar is never executed on insn 15. The "set = single_set (next)" also bypasses that insn 15 is a PARALLEL with a CLOBBER of a general purpose register. Appears the code is in postreload since 2003, when postreload.c was split out of reload1.c.
next prev parent reply other threads:[~2023-05-28 19:26 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-24 7:36 [Bug c/101188] New: [AVR] Miscompilation and function pointers joel.bertrand at systella dot fr 2021-06-25 8:09 ` [Bug target/101188] " saaadhu at gcc dot gnu.org 2023-05-24 6:56 ` gjl at gcc dot gnu.org 2023-05-24 7:21 ` [Bug rtl-optimization/101188] " gjl at gcc dot gnu.org 2023-05-24 7:44 ` gjl at gcc dot gnu.org 2023-05-24 11:07 ` gjl at gcc dot gnu.org 2023-05-24 19:07 ` gjl at gcc dot gnu.org 2023-05-25 9:47 ` gjl at gcc dot gnu.org 2023-05-28 9:24 ` [Bug rtl-optimization/101188] [postreload] Uses content of a clobbered register gjl at gcc dot gnu.org 2023-05-28 19:26 ` gjl at gcc dot gnu.org [this message] 2023-05-29 19:35 ` gjl at gcc dot gnu.org 2023-05-30 19:05 ` gjl at gcc dot gnu.org 2023-06-02 10:36 ` uweigand at gcc dot gnu.org 2023-06-02 11:27 ` gjl at gcc dot gnu.org 2023-06-02 15:35 ` uweigand at gcc dot gnu.org 2023-06-12 18:55 ` cvs-commit at gcc dot gnu.org 2023-06-13 11:42 ` gjl at gcc dot gnu.org 2023-06-13 11:45 ` gjl at gcc dot gnu.org 2023-08-09 18:57 ` gjl at gcc dot gnu.org 2024-02-09 11:23 ` [Bug rtl-optimization/101188] [11/12/13 Regression] " gjl at gcc dot gnu.org 2024-02-09 13:02 ` rguenth at gcc dot gnu.org 2024-05-08 11:47 ` rguenth 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-101188-4-xqYk7QQ2tC@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).