public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xry111 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/113204] lto1: error: qsort comparator non-negative on sorted output: 64
Date: Fri, 02 Feb 2024 07:27:04 +0000 [thread overview]
Message-ID: <bug-113204-4-gE76BfNgdn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113204-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113204
Xi Ruoyao <xry111 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |xry111 at gcc dot gnu.org
Keywords| |testsuite-fail
--- Comment #5 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
I've hit a similar ICE testing libbacktrace with LTO bootstrapped GCC on
LoongArch:
during IPA pass: static-var
lto1: internal compiler error: qsort checking failed
0x7ffff1b13047 __libc_start_call_main
../sysdeps/nptl/libc_start_call_main.h:58
0x7ffff1b1316f __libc_start_main_impl
/sources/glibc-2.39/csu/libc-start.c:360
0x12019a547 _start
../sysdeps/loongarch/start.S:75
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
lto-wrapper: fatal error: /sources/gcc-14-8722+hotfix/build/./prev-gcc/xgcc
returned 1 exit status
compilation terminated.
/usr/bin/ld: error: lto-wrapper failed
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:1340: btest_lto] Error 1
Unfortunately I didn't enable the debug info. I'll keep my build tree and try
to gather some info when I get some time...
next prev parent reply other threads:[~2024-02-02 7:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 18:44 [Bug lto/113204] New: [14 Regression] " doko at gcc dot gnu.org
2024-01-02 18:51 ` [Bug lto/113204] " pinskia at gcc dot gnu.org
2024-01-06 6:15 ` pinskia at gcc dot gnu.org
2024-01-06 9:35 ` sjames at gcc dot gnu.org
2024-01-06 9:35 ` sjames at gcc dot gnu.org
2024-01-06 9:47 ` [Bug lto/113204] " pinskia at gcc dot gnu.org
2024-01-08 14:40 ` rguenth at gcc dot gnu.org
2024-02-02 7:27 ` xry111 at gcc dot gnu.org [this message]
2024-03-16 4:34 ` sjames at gcc dot gnu.org
2024-03-16 4:37 ` sjames at gcc dot gnu.org
2024-03-16 4:39 ` sjames 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-113204-4-gE76BfNgdn@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).