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: Wed, 27 Mar 2024 17:01:11 +0000 [thread overview]
Message-ID: <bug-114452-4-alMWMxohf9@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
Martin Jambor <jamborm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|DUPLICATE |---
Last reconfirmed| |2024-03-27
Ever confirmed|0 |1
--- Comment #4 from Martin Jambor <jamborm at gcc dot gnu.org> ---
This does not look like a duplicate of PR 111573.
Nevertheless, it is not quite obvious what to do here. Inlining
happens before unrolling and I am not sure we'd consider unrolling in
early optimizations. And without unrolling, the load from the array
is not easy to fold.
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?
next prev parent reply other threads:[~2024-03-27 17:01 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 [this message]
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
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-alMWMxohf9@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).