From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id D6CA63857C7D; Thu,  7 Dec 2023 08:44:07 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D6CA63857C7D
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1701938647;
	bh=OxG6MPGuMj6ABE4Gap1qsKl6DgUZRcyRZJQVCtrGo5U=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=agjk+i7/sS9mQoMa2YZRW+u3iBc/T7bhVJ0i+hHGnbwO9LBrlme3/s/hJa78dH7Ra
	 0MvQakUoLooeqmSl5Dp5vI5hA2qZs3ncRRzDkJ1IoyvqiArEicb/aVpkYibE7amABS
	 2DLwAiN+EUtpulGekFb85JHxyxOMJsTwaebDB7aw=
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/112788] [14 regression] ICEs in fold_range,
 at range-op.cc:206 after r14-5972-gea19de921b01a6
Date: Thu, 07 Dec 2023 08:43:52 +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: build, ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: linkw at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: linkw at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 14.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-112788-4-xnNoSSYCMr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-112788-4@http.gcc.gnu.org/bugzilla/>
References: <bug-112788-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D112788

--- Comment #5 from Kewen Lin <linkw at gcc dot gnu.org> ---
One workaround patch was posted at
https://gcc.gnu.org/pipermail/gcc-patches/2023-December/639140.html.

We also found that with default long double format ieee128 the culprit comm=
it
caused the libquadmath library isn't able to be built on a system with ieee=
128
libs, consequently there are a lot of fortran testing failures.

The workaround also fixed some failures which existed there previously:

UNRESOLVED->NA: 20_util/from_chars/8.cc  -std=3Dgnu++23 compilation failed =
to
produce executable
NA->PASS: 20_util/from_chars/8.cc  -std=3Dgnu++23 execution test
FAIL->PASS: 20_util/from_chars/8.cc  -std=3Dgnu++23 (test for excess errors)
UNRESOLVED->NA: 20_util/from_chars/8.cc  -std=3Dgnu++26 compilation failed =
to
produce executable
NA->PASS: 20_util/from_chars/8.cc  -std=3Dgnu++26 execution test
FAIL->PASS: 20_util/from_chars/8.cc  -std=3Dgnu++26 (test for excess errors)
UNRESOLVED->NA: 20_util/to_chars/float128_c++23.cc  -std=3Dgnu++23 compilat=
ion
failed to produce executable
NA->PASS: 20_util/to_chars/float128_c++23.cc  -std=3Dgnu++23 execution test
FAIL->PASS: 20_util/to_chars/float128_c++23.cc  -std=3Dgnu++23 (test for ex=
cess
errors)
UNRESOLVED->NA: 20_util/to_chars/float128_c++23.cc  -std=3Dgnu++26 compilat=
ion
failed to produce executable
NA->PASS: 20_util/to_chars/float128_c++23.cc  -std=3Dgnu++26 execution test
FAIL->PASS: 20_util/to_chars/float128_c++23.cc  -std=3Dgnu++26 (test for ex=
cess
errors)=