From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 76F82385E004; Wed, 14 Feb 2024 13:54:10 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 76F82385E004 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1707918850; bh=vTbofeed4/UQCFL3WxlfCSIxEUGwp904CImrNPjdapk=; h=From:To:Subject:Date:In-Reply-To:References:From; b=kgfkc1h+DWpP5+f6qvuOn11ie/ghqjG9+2n5ChKwTm+Gp0OR8X5ryXzNSFD0NqWKp cxj+jFgNXJjckpBY6AJ+HtwEkUvUfr+l9laM4es/4xRaAQLpa/oj7eY11BVyD3vTWp ImtRw3XBrs+86VlCVWNbDj4Ptljbdi9sOgz9k1/k= From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/113576] [14 regression] 502.gcc_r hangs r14-8223-g1c1853a70f9422169190e65e568dcccbce02d95c Date: Wed, 14 Feb 2024 13:54:09 +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: 14.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org X-Bugzilla-Target-Milestone: 14.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 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D113576 --- Comment #49 from Richard Biener --- (In reply to Uro=C5=A1 Bizjak from comment #48) > The runtime testcase fails on non-AVX512F x86 targets due to: >=20 > /* { dg-do run } */ > /* { dg-options "-O3" } */ > /* { dg-additional-options "-march=3Dskylake-avx512" { target { x86_64-*-* > i?86-*-* } } } */ >=20 > but check_vect() only checks runtime support up to AVX2. Hmm, can we fix that? We could change the above to { target avx512f_runtim= e } but that really only checks for AVX512F, not say AVX512VL ... I do remember using -mavx512vl wasn't enough to trigger the miscompile nor did it trigger with -march=3Dznver4 ... so I stuck to skylake-avx512 :/=