From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 50A06385842D; Mon, 1 Nov 2021 11:29:50 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 50A06385842D From: "jakub at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/103006] [9/10/11/12 Regression] wrong code at -O1 or -O2 on x86_64-linux-gnu by r7-7101 Date: Mon, 01 Nov 2021 11:29:50 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: rtl-optimization X-Bugzilla-Version: unknown X-Bugzilla-Keywords: ra, wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 9.5 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Nov 2021 11:29:50 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D103006 Jakub Jelinek changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rguenth at gcc dot gnu.org --- Comment #5 from Jakub Jelinek --- What we see is an effect of 3 different optimizations, one is loop unrolling (cunroll in this case), another one is ivopts that moves the h array refere= nces out of the loops but still has separate: ivtmp.40_47 =3D (unsigned long) &h; _17 =3D (unsigned long) &h; _30 =3D _17 + 96; ... h =3D{v} {CLOBBER}; ivtmp.30_33 =3D (unsigned long) &h; _41 =3D (unsigned long) &h; _36 =3D _41 + 96; and finally dom3's VN which replaces ivtmp.30_33 initializer with ivtmp.40_= 47 and _36 with _30. If what the cfg expand var partition code is as designed (I think other pas= ses do it too, e.g. compute_live_vars/live_vars_at_stmt relies on it too), then= we need to somehow avoid VN of &var across var =3D{v} {CLOBBER} stmt, but it i= sn't really clear to me how. Unless we change loop unrolling so that the different loop iterations if th= ere is a var clobber in the loop actually have different variables (the first iteration the original var and other iterations that var's copies; perhaps = only for addressable vars?). Then naturally VN couldn't merge those and the RTL partitioning code could decide to put them into the same or different parti= tion and later RTL opts could CSE the addresses.=