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: Mon, 29 May 2023 19:35:08 +0000	[thread overview]
Message-ID: <bug-101188-4-pdZxg4cImj@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 #10 from Georg-Johann Lay <gjl at gcc dot gnu.org> ---
Created attachment 55189
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55189&action=edit
Proposed patch for postreload.cc so analysis is not bypassing "next" insn.

(In reply to Georg-Johann Lay from comment #9)
> 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.

A simple solution is to not "insn = next;" and just to pseudo-delete insn so
that NEXT_INSN (insn) works in the for loop:

diff --git a/gcc/postreload.cc b/gcc/postreload.cc
index fb392651e1b..388b8c0a506 100644
--- a/gcc/postreload.cc
+++ b/gcc/postreload.cc
@@ -2031,9 +2031,8 @@ reload_cse_move2add (rtx_insn *first)
                            }
                        }
                      if (success)
-                       delete_insn (insn);
+                       SET_INSN_DELETED (insn);
                      changed |= success;
-                     insn = next;
                      move2add_record_mode (reg);
                      reg_offset[regno]
                        = trunc_int_for_mode (added_offset + base_offset,

  parent reply	other threads:[~2023-05-29 19:35 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
2023-05-29 19:35 ` gjl at gcc dot gnu.org [this message]
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-pdZxg4cImj@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: link
Be 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).