public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/106943] GCC building clang/llvm with LTO flags causes ICE in clang
Date: Fri, 12 May 2023 14:09:46 +0000 [thread overview]
Message-ID: <bug-106943-4-UCRNwERxxt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106943-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106943
Jan Hubicka <hubicka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hubicka at gcc dot gnu.org
--- Comment #13 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
> What's the current best practice for LTO debugging? I don't imagine there's an > easy way to identify which of 2000 lto1 invocation crashes, or attach gdb to it? Or at least generate a corefile
What I do is to compile with --save-temps --verbose and then one can see which
ltrans ICEd in error message from internal make. The dump also contains all of
ltrans command lines (sometimes garbled by parallel output unoless you are
willing to wait for -flto=1). Invoke the corresponding ltrnans command line
from gdb and wait for crash.
Indeed it is quite long time problem with clang not building with lifetime DSE
and strict aliasing. I wonder why this is not fixed on clang side?
next prev parent reply other threads:[~2023-05-12 14:09 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 17:39 [Bug c++/106943] New: " immoloism at googlemail dot com
2022-09-14 17:39 ` [Bug c++/106943] " immoloism at googlemail dot com
2022-09-14 17:50 ` pinskia at gcc dot gnu.org
2022-09-14 19:49 ` immoloism at googlemail dot com
2022-09-15 7:17 ` rguenth at gcc dot gnu.org
2022-09-19 14:12 ` immoloism at googlemail dot com
2023-05-11 12:49 ` amonakov at gcc dot gnu.org
2023-05-11 19:39 ` amonakov at gcc dot gnu.org
2023-05-11 20:29 ` amonakov at gcc dot gnu.org
2023-05-12 13:14 ` xry111 at gcc dot gnu.org
2023-05-12 13:27 ` amonakov at gcc dot gnu.org
2023-05-12 13:32 ` xry111 at gcc dot gnu.org
2023-05-12 14:00 ` amonakov at gcc dot gnu.org
2023-05-12 14:09 ` hubicka at gcc dot gnu.org [this message]
2023-05-12 14:23 ` amonakov at gcc dot gnu.org
2023-05-12 14:29 ` Jan Hubicka
2023-05-12 14:29 ` hubicka at ucw dot cz
2023-05-12 14:41 ` xry111 at gcc dot gnu.org
2023-05-12 14:57 ` amonakov at gcc dot gnu.org
2023-05-12 15:16 ` xry111 at gcc dot gnu.org
2023-05-12 15:29 ` hubicka at ucw dot cz
2023-05-12 15:45 ` xry111 at gcc dot gnu.org
2023-05-12 15:48 ` amonakov at gcc dot gnu.org
2023-05-12 15:55 ` amonakov at gcc dot gnu.org
2023-05-12 16:56 ` pinskia at gcc dot gnu.org
2023-05-12 19:10 ` amonakov at gcc dot gnu.org
2023-05-12 19:19 ` pinskia at gcc dot gnu.org
2023-05-12 19:27 ` amonakov at gcc dot gnu.org
2023-05-12 19:30 ` pinskia at gcc dot gnu.org
2023-05-13 3:18 ` xry111 at gcc dot gnu.org
2023-05-13 3:19 ` xry111 at gcc dot gnu.org
2023-05-13 5:29 ` xry111 at gcc dot gnu.org
2023-05-13 6:30 ` amonakov at gcc dot gnu.org
2023-05-13 7:58 ` amonakov at gcc dot gnu.org
2023-05-13 20:06 ` xry111 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-106943-4-UCRNwERxxt@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).