From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 1AD88385C417; Wed, 6 Oct 2021 13:10:56 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1AD88385C417 From: "aldyh at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/102622] [12 Regression] Wrong code with -O3 for skylake-avx512 and icelake-server by r12-3903 Date: Wed, 06 Oct 2021 13:10:56 +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: 12.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: aldyh at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 12.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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: Wed, 06 Oct 2021 13:10:57 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D102622 --- Comment #7 from Aldy Hernandez --- (In reply to H.J. Lu from comment #6) > (In reply to Aldy Hernandez from comment #4) > > Can you try with -fno-thread-jumps to make sure its really the threader= at > > play? >=20 > -fno-thread-jumps fixes the bug. >=20 > > If so, you could try to narrow it down to the problematic threading path > > with: > >=20 > > -fdbg-cnt=3Dregistered_jump_thread:N:N > >=20 > > where N is the number that causes the problem. >=20 > What N should I try? I got >=20 > [hjl@gnu-skx-1 gcc]$ ./xgcc -B./ -S -O3 -march=3Dnative > /export/project/git/gcc-bisect/pr102622.cc > -fdbg-cnt=3Dregistered_jump_thread:10:10 > cc1plus: error: Interval overlap of ??-fdbg-cnt=3Dregistered_jump_thread?= ?: > [1, 10] and [1, 10] What I usually do is start with say...10 -fdbg-cnt=3Dregistered_jump_thread:10 and keep reducing it until you find the problematic one. Say it dies with 10, but does not with 9. That usually means that the combination of the first 10 jump threading paths caused the problem. More often than not, it means it's the 10th one. But it could be a combination = of 1-10. You could then further reduce it to an individual jump threading path (if you're lucky enough that's only one threading path that's causing the probl= em-- it's usually the case). For instance: -fdbg-cnt=3Dregistered_jump_thread:5-5 That will ONLY jump thread the 5th attempt. If that fails, then you're absolutely sure it's the 5th attempt that's causing the problem.=