public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "stefansf at linux dot ibm.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/111462] [14 regression] gcc.dg/tree-ssa/ssa-sink-18.c fails after r14-4089-gd45ddc2c04e471
Date: Tue, 19 Sep 2023 13:53:39 +0000 [thread overview]
Message-ID: <bug-111462-4-AqlwTmDpZC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111462-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111462
Stefan Schulze Frielinghaus <stefansf at linux dot ibm.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |stefansf at linux dot ibm.com
--- Comment #4 from Stefan Schulze Frielinghaus <stefansf at linux dot ibm.com> ---
Since r14-4089-gd45ddc2c04e471 bootstrap fails on s390 with
/devel/gcc/build/./prev-gcc/xg++ -B/devel/gcc/build/./prev-gcc/
-B/devel/gcc/dst/s390x-ibm-linux-gnu/bin/ -nostdinc++
-B/devel/gcc/build/prev-s390x-ibm-linux-gnu/libstdc++-v3/src/.libs
-B/devel/gcc/build/prev-s390x-ibm-linux-gnu/libstdc++-v3/libsupc++/.libs
-I/devel/gcc/build/prev-s390x-ibm-linux-gnu/libstdc++-v3/include/s390x-ibm-linux-gnu
-I/devel/gcc/build/prev-s390x-ibm-linux-gnu/libstdc++-v3/include
-I/devel/gcc/src/libstdc++-v3/libsupc++
-L/devel/gcc/build/prev-s390x-ibm-linux-gnu/libstdc++-v3/src/.libs
-L/devel/gcc/build/prev-s390x-ibm-linux-gnu/libstdc++-v3/libsupc++/.libs
-I/devel/gcc/src/libcpp -I. -I/devel/gcc/src/libcpp/../include
-I/devel/gcc/src/libcpp/include -g -O2 -fchecking=1 -W -Wall -Wno-narrowing
-Wwrite-strings -Wmissing-format-attribute -pedantic -Wno-long-long -Werror
-fno-exceptions -fno-rtti -I/devel/gcc/src/libcpp -I.
-I/devel/gcc/src/libcpp/../include -I/devel/gcc/src/libcpp/include -c -o
line-map.o -MT line-map.o -MMD -MP -MF .deps/line-map.Tpo
/devel/gcc/src/libcpp/line-map.cc
/devel/gcc/src/libcpp/line-map.cc: In function 'int
linemap_compare_locations(line_maps*, location_t, location_t)':
/devel/gcc/src/libcpp/line-map.cc:1434:1: error: statement uses released SSA
name
1434 | linemap_compare_locations (line_maps *set,
| ^~~~~~~~~~~~~~~~~~~~~~~~~
_219 = _216;
The use of _216 should have been replaced
during GIMPLE pass: dom
/devel/gcc/src/libcpp/line-map.cc:1434:1: internal compiler error: cannot
update SSA form
If you think it might be helpful to reduce line-map.cc then just give me a
ping.
next prev parent reply other threads:[~2023-09-19 13:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 17:49 [Bug tree-optimization/111462] New: " seurer at gcc dot gnu.org
2023-09-18 17:58 ` [Bug testsuite/111462] " pinskia at gcc dot gnu.org
2023-09-18 18:01 ` seurer at gcc dot gnu.org
2023-09-19 8:57 ` rguenth at gcc dot gnu.org
2023-09-19 13:53 ` stefansf at linux dot ibm.com [this message]
2023-09-19 14:22 ` rguenth at gcc dot gnu.org
2023-09-19 15:30 ` stefansf at linux dot ibm.com
2023-10-17 12:56 ` rguenth at gcc dot gnu.org
2023-10-25 20:31 ` seurer at gcc dot gnu.org
2023-10-30 10:01 ` rguenth at gcc dot gnu.org
2023-10-30 10:03 ` cvs-commit at gcc dot gnu.org
2023-10-30 10:03 ` rguenth at gcc dot gnu.org
2023-11-10 14:28 ` rguenth at gcc dot gnu.org
2024-02-07 22:21 ` seurer at gcc dot gnu.org
2024-02-28 11:12 ` cvs-commit at gcc dot gnu.org
2024-02-28 11:13 ` jakub 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-111462-4-AqlwTmDpZC@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).