public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/114531] Feature proposal for an `-finline-functions-aggressive` compiler option Date: Tue, 25 Jun 2024 13:03:29 +0000 [thread overview] Message-ID: <bug-114531-4-Quqp085eAN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114531-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114531 Wilco <wilco at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wilco at gcc dot gnu.org --- Comment #10 from Wilco <wilco at gcc dot gnu.org> --- A 1.1% overall performance gain looks good - is there a significant codesize hit from this? If so, are there slightly less aggressive settings that still get most of the performance gains but at a lower (acceptable) codesize cost? It seems there may be scope to improve the default settings of -O2.
next prev parent reply other threads:[~2024-06-25 13:03 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-30 1:25 [Bug driver/114531] New: " rvmallad at amazon dot com 2024-03-30 1:37 ` [Bug ipa/114531] " pinskia at gcc dot gnu.org 2024-03-30 1:38 ` pinskia at gcc dot gnu.org 2024-03-30 1:56 ` pinskia at gcc dot gnu.org 2024-03-30 2:19 ` rvmallad at amazon dot com 2024-03-30 2:21 ` rvmallad at amazon dot com 2024-03-30 2:29 ` pinskia at gcc dot gnu.org 2024-04-01 11:41 ` rvmallad at amazon dot com 2024-04-02 8:36 ` rguenth at gcc dot gnu.org 2024-04-08 9:52 ` rvmallad at amazon dot com 2024-05-31 13:57 ` rvmallad at amazon dot com 2024-06-25 13:03 ` wilco at gcc dot gnu.org [this message] 2024-06-25 15:30 ` rvmallad at amazon dot com 2024-06-25 16:20 ` hubicka at ucw dot cz 2024-06-25 16:25 ` rvmallad at amazon dot com 2024-06-25 16:49 ` hubicka at ucw dot cz 2024-06-25 17:40 ` rvmallad at amazon dot com 2024-06-25 17:48 ` rvmallad at amazon dot com 2024-06-25 18:40 ` rsandifo at gcc dot gnu.org 2024-06-25 22:25 ` Jan Hubicka 2024-06-25 22:25 ` hubicka at ucw dot cz 2024-06-27 11:46 ` rvmallad at amazon 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-114531-4-Quqp085eAN@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: linkBe 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).