public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amonakov 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 15:55:14 +0000	[thread overview]
Message-ID: <bug-106943-4-zmmIGMS7IK@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

--- Comment #22 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
(In reply to Jan Hubicka from comment #19)
> It would be really nice to have the ranger bug fixed.  Since lifetime
> DSE is all handled in C++ FE there is no good reason why it should not
> work to LTO togehter objects compiled with the flag and without...

Wait. There's absolutely no connection between lifetime-dse and the ranger
issue uncovered by -flto-partition=1to1. Selective -fno-lifetime-dse surely
works, as you said it's fully handled by the front-end. I was just saying that
applying -fno-lifetime-dse to User.cpp is insufficient because problematic
codegen happens in other translation units (where objects of class User are
constructed).

Fully agreed that fixing the ranger bug would be nice regardless.

> llvm is really nice benchmark for LTO and PGO, so it would be nice if it
> was not fragile and built with -O3 -flto.  In my testing GCC produced
> binary with LTO+PGO is a lot smaller. It seems to also generate code
> faster but parsing is bit slower, which I think may be related to
> -fstrict-aliasing.

Makes sense I guess.

  parent reply	other threads:[~2023-05-12 15:55 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
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 [this message]
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-zmmIGMS7IK@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).