From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id E9312385840D; Tue, 30 Jan 2024 06:49:29 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E9312385840D DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1706597369; bh=vLyjWXBc84JFBgki7CkBRt5bCW3aHsRseEzUAOBbqi4=; h=From:To:Subject:Date:In-Reply-To:References:From; b=iof/YNt0sW8MJ1UgKnjNE4pbIbn33hAKsC3N6ugffX3Ih7fL+WZ7OCui7DY9HMC1B vHLQ8Ej11zZ69JXiiawUC8No66IbDuH2j8UldHpRuO3RgbypgyehQC2uAhxYH64mvH zC9nJeJXswvhJGq4/Yi4NOobOUGESllLdBHrJPOE= From: "haochen.jiang at intel dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/113656] [x86] ICE in simplify_const_unary_operation, at simplify-rtx.cc:1954 with new -mavx10.1 Date: Tue, 30 Jan 2024 06:49:29 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: haochen.jiang at intel dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- 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=3D113656 --- Comment #3 from Haochen Jiang --- (In reply to Haochen Jiang from comment #2) > Actually it is caused by option -funsafe-math-optimizations but not > -mavx10.1. >=20 > Before my commit, while using option: >=20 > -frounding-math -O3 -mavx512fp16 -mavx512vl -funsafe-math-optimizations >=20 > It will also report ICE. In GCC13.2, it won't, which means it is introduc= ed > in GCC14. >=20 > You got that bisect result since it is when avx10.1 first introduced. > -mavx10.1 will enable -mavx512fp16 and -mavx512vl. >=20 > When we eliminate -funsafe-math-optimizations, it will be ok. >=20 > Also if we are only using -mavx512vl, everything is ok. Seems like someth= ing > got disabled under -mavx512fp16. What I mean "disabled" here is actually not enabled while using -funsafe-math-optimizations with -mavx512fp16. >=20 > Need more bisect with option: -frounding-math -O3 -mavx512fp16 -mavx512vl > -funsafe-math-optimizations to find out why.=