public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/113712] [11/12/13/14 Regression] lto crash: when building 641.leela_s peek with Example-gcc-linux-x86.cfg (SPEC2017 1.1.9) since r10-3311-gff6686d2e5f797
Date: Mon, 12 Feb 2024 17:15:58 +0000 [thread overview]
Message-ID: <bug-113712-4-ablHdG03EX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113712-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113712
--- Comment #18 from Martin Jambor <jamborm at gcc dot gnu.org> ---
(In reply to Filip Kastl from comment #17)
> I've bisected this (using the test from Andrew Pinski) to
> r10-3311-gff6686d2e5f797
That's a coincidence, with -fno-ipa-sra the testcase fails even earlier,
IPA-SRA was just hiding it, most probably by localizing some symbol before the
linking stage.
Bugs that are only reproducible with -fno-use-linker-plugin are unlikely to get
a high priority. But I understand that the original issue does not need it?
(Also, the issue is supposed to be reproducible ton x86_64-linux, right?)
next prev parent reply other threads:[~2024-02-12 17:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 1:57 [Bug lto/113712] New: lto crash: when building 641.leela_s peek with Example-gcc-linux-x86.cfg (SPEC2017 1.1.9) lehua.ding at rivai dot ai
2024-02-02 2:18 ` [Bug lto/113712] " lehua.ding at rivai dot ai
2024-02-02 2:32 ` pinskia at gcc dot gnu.org
2024-02-02 3:22 ` lehua.ding at rivai dot ai
2024-02-02 3:34 ` pinskia at gcc dot gnu.org
2024-02-02 4:09 ` lehua.ding at rivai dot ai
2024-02-02 4:11 ` lehua.ding at rivai dot ai
2024-02-02 4:33 ` pinskia at gcc dot gnu.org
2024-02-02 4:41 ` pinskia at gcc dot gnu.org
2024-02-02 4:44 ` pinskia at gcc dot gnu.org
2024-02-02 4:49 ` pinskia at gcc dot gnu.org
2024-02-02 5:03 ` lehua.ding at rivai dot ai
2024-02-02 5:07 ` lehua.ding at rivai dot ai
2024-02-02 5:21 ` pinskia at gcc dot gnu.org
2024-02-02 16:58 ` pinskia at gcc dot gnu.org
2024-02-02 19:09 ` pinskia at gcc dot gnu.org
2024-02-02 19:10 ` [Bug lto/113712] [11/12/13/14 Regression] " pinskia at gcc dot gnu.org
2024-02-05 8:25 ` rguenth at gcc dot gnu.org
2024-02-11 14:44 ` pheeck at gcc dot gnu.org
2024-02-12 17:15 ` jamborm at gcc dot gnu.org [this message]
2024-02-12 17:25 ` [Bug lto/113712] [11/12/13/14 Regression] lto crash: when building 641.leela_s peek with Example-gcc-linux-x86.cfg (SPEC2017 1.1.9) since r10-3311-gff6686d2e5f797 pinskia at gcc dot gnu.org
2024-02-12 18:00 ` jamborm 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-113712-4-ablHdG03EX@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).