public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/116410] modref doesn't generate LTO summaries with -ffat-lto-objects (-ffat-lto-objects generates different and inefficient code compared with -fno-fat-lto-objects)
Date: Thu, 05 Sep 2024 14:48:54 +0000 [thread overview]
Message-ID: <bug-116410-4-KbTqSLq5Yz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-116410-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116410
--- Comment #16 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by H.J. Lu <hjl@gcc.gnu.org>:
https://gcc.gnu.org/g:e83df98c8142235cda0bcd538907a4693e420c92
commit r13-9006-ge83df98c8142235cda0bcd538907a4693e420c92
Author: H.J. Lu <hjl.tools@gmail.com>
Date: Tue Aug 27 13:11:39 2024 -0700
ipa: Don't disable function parameter analysis for fat LTO
Update analyze_parms not to disable function parameter analysis for
-ffat-lto-objects. Tested on x86-64, there are no differences in zstd
with "-O2 -flto=auto" -g "vs -O2 -flto=auto -g -ffat-lto-objects".
PR ipa/116410
* ipa-modref.cc (analyze_parms): Always analyze function parameter
for LTO.
Signed-off-by: H.J. Lu <hjl.tools@gmail.com>
(cherry picked from commit 2f1689ea8e631ebb4ff3720d56ef0362f5898ff6)
next prev parent reply other threads:[~2024-09-05 14:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 3:42 [Bug ipa/116410] New: fat-lto-objects generates different and inefficient code compared with no-fat-lto-objects yinyuefengyi at gmail dot com
2024-08-19 3:44 ` [Bug ipa/116410] " yinyuefengyi at gmail dot com
2024-08-19 3:45 ` yinyuefengyi at gmail dot com
2024-08-19 15:04 ` [Bug ipa/116410] -ffat-lto-objects generates different and inefficient code compared with -fno-fat-lto-objects rguenth at gcc dot gnu.org
2024-08-21 3:29 ` yinyuefengyi at gmail dot com
2024-08-27 17:33 ` hjl.tools at gmail dot com
2024-08-27 17:39 ` hjl.tools at gmail dot com
2024-08-27 20:13 ` hjl.tools at gmail dot com
2024-08-28 2:47 ` yinyuefengyi at gmail dot com
2024-09-02 5:26 ` sjames at gcc dot gnu.org
2024-09-02 7:18 ` [Bug ipa/116410] modref doesn't generate LTO summaries with -ffat-lto-objects (-ffat-lto-objects generates different and inefficient code compared with -fno-fat-lto-objects) rguenth at gcc dot gnu.org
2024-09-02 7:26 ` sjames at gcc dot gnu.org
2024-09-03 11:04 ` hubicka at ucw dot cz
2024-09-03 12:55 ` cvs-commit at gcc dot gnu.org
2024-09-03 13:10 ` sjames at gcc dot gnu.org
2024-09-03 14:20 ` hjl.tools at gmail dot com
2024-09-05 14:31 ` cvs-commit at gcc dot gnu.org
2024-09-05 14:48 ` cvs-commit at gcc dot gnu.org [this message]
2024-09-05 15:03 ` cvs-commit at gcc dot gnu.org
2024-09-05 15:04 ` hjl.tools 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-116410-4-KbTqSLq5Yz@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).