From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 39273386101D; Mon, 16 Nov 2020 10:48:17 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 39273386101D From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/97821] [8/9/10/11 Regression] wrong code with -ftree-vectorize at -O1 on x86_64-pc-linux-gnu by r6-3608 Date: Mon, 16 Nov 2020 10:48:17 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 11.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 8.5 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: keywords priority 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, 16 Nov 2020 10:48:17 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D97821 Richard Biener changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |wrong-code Priority|P3 |P2 CC| |matz at gcc dot gnu.org --- Comment #3 from Richard Biener --- Hmm. It takes quite some time for us to elide the dead stores to bd, ar an= d at (and only ar and at are vectorized). I guess we run into some alias-walk limits of DCE and vectorizing the stores fixes that. Unfortunately those limits are hard-coded: if (/* Constant but quadratic for small functions. */ total_chain > 128 * 128 /* Linear in the number of may-defs. */ && total_chain > 32 * longest_chain /* Linear in the number of uses. */ && total_chain > nr_walks * 32) { this points to the known issue of stack var coalescing with CLOBBERs and indeed -fstack-reuse=3Dnone fixes the testcase, without actually spotting the bad coalescing. So related to that duplicate bug we have about this issue.=