public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "immoloism at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/106943] New: GCC building clang/llvm with LTO flags causes ICE in clang
Date: Wed, 14 Sep 2022 17:39:28 +0000 [thread overview]
Message-ID: <bug-106943-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106943
Bug ID: 106943
Summary: GCC building clang/llvm with LTO flags causes ICE in
clang
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: immoloism at googlemail dot com
Target Milestone: ---
Created attachment 53574
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53574&action=edit
ICE error
I've found an interesting ICE which only occurs when LTO flags are turned on in
GCC while building clang and llvm while compiling compiler-rt-sanitizers. If I
rebuild clang/llvm without the flto cflags then the bug does not appear.
CFLAGS used to build clang/llvm "-march=native -O2 -pipe -fgraphite-identity
-floop-nest-optimize -flto=8 -fuse-linker-plugin -falign-functions=32"
This is the first time I've run into anything like this so please ask if any
other files or tests will help you identify the cause and I'd be happy to
oblige.
I have reported this to the LLVM team and they believe this could be an issue
your end so hopefully you have some ideas to add.
next reply other threads:[~2022-09-14 17:39 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 17:39 immoloism at googlemail dot com [this message]
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
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@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).