public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/114452] Functions invoked through compile-time table of function pointers not inlined
Date: Thu, 11 Apr 2024 09:33:46 +0000	[thread overview]
Message-ID: <bug-114452-4-je41jvvJvp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114452-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Martin Jambor <jamborm at gcc dot gnu.org> ---
(In reply to Paweł Bylica from comment #5)
> (In reply to Martin Jambor from comment #4)
> > In this testcase all (well, both) functions referenced from the array
> > are semantically equivalent which is recognized by ICF but making it
> > be able to pass this information to the inliner would be
> > non-trivial... and is this the common case worth optimizing for?
> 
> I reduced the original code to the array of two identical functions.
> Originally, there weren't identical. I can update the test case if this make
> more sense.

Probably not.  But how many elements does the array have in the original code? 
Perhaps we could speculatively inline them if there are only few.

  parent reply	other threads:[~2024-04-11  9:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-25 10:09 [Bug rtl-optimization/114452] New: " chfast at gmail dot com
2024-03-25 10:35 ` [Bug rtl-optimization/114452] " xry111 at gcc dot gnu.org
2024-03-25 10:40 ` chfast at gmail dot com
2024-03-25 10:41 ` xry111 at gcc dot gnu.org
2024-03-27 17:01 ` jamborm at gcc dot gnu.org
2024-03-27 17:03 ` xry111 at gcc dot gnu.org
2024-04-11  8:07 ` chfast at gmail dot com
2024-04-11  9:33 ` jamborm at gcc dot gnu.org [this message]
2024-04-11  9:41 ` chfast 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-114452-4-je41jvvJvp@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).