public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
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 [thread overview]
Message-ID: <bug-112788-4-xnNoSSYCMr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112788-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112788
--- 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 commit
caused the libquadmath library isn't able to be built on a system with ieee128
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=gnu++23 compilation failed to
produce executable
NA->PASS: 20_util/from_chars/8.cc -std=gnu++23 execution test
FAIL->PASS: 20_util/from_chars/8.cc -std=gnu++23 (test for excess errors)
UNRESOLVED->NA: 20_util/from_chars/8.cc -std=gnu++26 compilation failed to
produce executable
NA->PASS: 20_util/from_chars/8.cc -std=gnu++26 execution test
FAIL->PASS: 20_util/from_chars/8.cc -std=gnu++26 (test for excess errors)
UNRESOLVED->NA: 20_util/to_chars/float128_c++23.cc -std=gnu++23 compilation
failed to produce executable
NA->PASS: 20_util/to_chars/float128_c++23.cc -std=gnu++23 execution test
FAIL->PASS: 20_util/to_chars/float128_c++23.cc -std=gnu++23 (test for excess
errors)
UNRESOLVED->NA: 20_util/to_chars/float128_c++23.cc -std=gnu++26 compilation
failed to produce executable
NA->PASS: 20_util/to_chars/float128_c++23.cc -std=gnu++26 execution test
FAIL->PASS: 20_util/to_chars/float128_c++23.cc -std=gnu++26 (test for excess
errors)
next prev parent reply other threads:[~2023-12-07 8:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 18:54 [Bug other/112788] New: " seurer at gcc dot gnu.org
2023-11-30 18:57 ` [Bug tree-optimization/112788] " pinskia at gcc dot gnu.org
2023-12-01 7:23 ` rguenth at gcc dot gnu.org
2023-12-01 8:04 ` linkw at gcc dot gnu.org
2023-12-01 19:15 ` amacleod at redhat dot com
2023-12-03 13:28 ` tschwinge at gcc dot gnu.org
2023-12-04 1:52 ` linkw at gcc dot gnu.org
2023-12-07 8:43 ` linkw at gcc dot gnu.org [this message]
2023-12-13 2:40 ` cvs-commit at gcc dot gnu.org
2023-12-13 2:43 ` linkw at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-112788-4-xnNoSSYCMr@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).