public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kloczko.tomasz at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/106499] LTO runs forever in libfabric 1.15.1 linking
Date: Tue, 02 Aug 2022 10:24:23 +0000	[thread overview]
Message-ID: <bug-106499-4-pO7yTcBmGT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106499-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #15 from Tomasz Kłoczko <kloczko.tomasz at gmail dot com> ---
(In reply to Richard Biener from comment #14)
> In addition to that, -flto-partition=none is almost never a good idea either.
> 
> Note I think that we should honor flatten only during early inlining to
> avoid all kinds of funny behavior when applying cross TU.

Issue is that in few cases AFAIK it is only solution to some still unresolved
LTO issues :/

  parent reply	other threads:[~2022-08-02 10:24 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-01 16:09 [Bug lto/106499] New: " kloczko.tomasz at gmail dot com
2022-08-01 16:10 ` [Bug lto/106499] " kloczko.tomasz at gmail dot com
2022-08-01 16:30 ` pinskia at gcc dot gnu.org
2022-08-01 16:35 ` kloczko.tomasz at gmail dot com
2022-08-01 16:41 ` kloczko.tomasz at gmail dot com
2022-08-01 16:41 ` kloczko.tomasz at gmail dot com
2022-08-01 19:31 ` marxin at gcc dot gnu.org
2022-08-01 22:16 ` kloczko.tomasz at gmail dot com
2022-08-01 22:20 ` pinskia at gcc dot gnu.org
2022-08-01 22:43 ` kloczko.tomasz at gmail dot com
2022-08-01 22:56 ` pinskia at gcc dot gnu.org
2022-08-01 23:10 ` kloczko.tomasz at gmail dot com
2022-08-01 23:21 ` pinskia at gcc dot gnu.org
2022-08-02  7:47 ` kloczko.tomasz at gmail dot com
2022-08-02 10:07 ` rguenth at gcc dot gnu.org
2022-08-02 10:24 ` kloczko.tomasz at gmail dot com [this message]
2022-08-02 11:29 ` marxin at gcc dot gnu.org
2022-08-02 13:14 ` kloczko.tomasz at gmail dot com
2022-08-02 13:22 ` marxin at gcc dot gnu.org
2022-08-02 13:37 ` kloczko.tomasz at gmail dot com
2022-08-02 13:42 ` marxin at gcc dot gnu.org
2022-08-02 19:23 ` kloczko.tomasz at gmail dot com
2022-08-02 19:34 ` kloczko.tomasz at gmail dot com
2022-08-03  9:06 ` marxin at gcc dot gnu.org
2022-08-03 11:03 ` kloczko.tomasz at gmail dot com

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-106499-4-pO7yTcBmGT@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).