public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sam at gentoo dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/105600] [12/13 Regression] ICE with LTO when building Mumble since r12-5696-g53caa4723d8de73f
Date: Wed, 18 May 2022 22:15:25 +0000	[thread overview]
Message-ID: <bug-105600-4-FCAMDeXsJw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105600-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from Sam James <sam at gentoo dot org> ---
Thanks Andrew. I spent a while trying to minimise it using that but I've got a
bit stuck. I'm used to reducing normal ICEs but link-time/LTO ones seem to be
harder to me.

I was going to upload the full lot with -save-temps and hope that might be
enough if I couldn't get further.

Thanks Alex - I've been setting up a Docker file for you to try out (although
was going to try clean up the env to give you access to the box too), but so
glad to see you guys have managed to get further.

Please tell me if I am needed to try and squeeze more out, although I'm likely
to need instructions given aforementioned.

  parent reply	other threads:[~2022-05-18 22:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-13 21:13 [Bug lto/105600] New: ICE with LTO when building Mumble from git on arm64 sam at gentoo dot org
2022-05-13 21:55 ` [Bug lto/105600] " pinskia at gcc dot gnu.org
2022-05-17 10:18 ` [Bug ipa/105600] " acoplan at gcc dot gnu.org
2022-05-17 10:29 ` acoplan at gcc dot gnu.org
2022-05-18  9:25 ` acoplan at gcc dot gnu.org
2022-05-18  9:26 ` acoplan at gcc dot gnu.org
2022-05-18  9:50 ` acoplan at gcc dot gnu.org
2022-05-18 11:04 ` marxin at gcc dot gnu.org
2022-05-18 11:40 ` [Bug ipa/105600] [12/13 Regression] ICE with LTO when building Mumble since r12-5696-g53caa4723d8de73f marxin at gcc dot gnu.org
2022-05-18 12:09 ` marxin at gcc dot gnu.org
2022-05-18 22:15 ` sam at gentoo dot org [this message]
2022-05-19  7:11 ` marxin at gcc dot gnu.org
2022-05-19  7:44 ` acoplan at gcc dot gnu.org
2022-05-20  7:02 ` [Bug ipa/105600] [9/10/11/12/13 " rguenth at gcc dot gnu.org
2022-05-20  9:22 ` [Bug ipa/105600] [9/10/11/12/13 Regression] ICE with LTO when building Mumble acoplan at gcc dot gnu.org
2022-05-20 11:44 ` marxin at gcc dot gnu.org
2022-05-27  9:48 ` [Bug ipa/105600] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-23  4:08 ` cvs-commit at gcc dot gnu.org
2022-06-23  4:08 ` [Bug ipa/105600] [10/11/12 " marxin at gcc dot gnu.org
2022-06-23 10:10 ` cvs-commit at gcc dot gnu.org
2022-06-23 10:12 ` cvs-commit at gcc dot gnu.org
2022-06-23 10:12 ` marxin 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-105600-4-FCAMDeXsJw@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).