From: "H.J. Lu" <hjl.tools@gmail.com>
To: rep.dot.nop@gmail.com
Cc: gcc-patches@gcc.gnu.org, Jan Hubicka <hubicka@ucw.cz>
Subject: Re: [PATCH v3] tree-profile: Disable indirect call profiling for IFUNC resolvers
Date: Thu, 4 Apr 2024 18:03:05 -0700 [thread overview]
Message-ID: <CAMe9rOof8vABTYU33mogvAEzaOmzaTihApUu3wdONiNmw_K0hA@mail.gmail.com> (raw)
In-Reply-To: <F461B0AE-2892-44AE-8820-C84A9E2116A8@gmail.com>
On Thu, Apr 4, 2024 at 5:34 PM <rep.dot.nop@gmail.com> wrote:
>
> On 3 April 2024 15:49:13 CEST, "H.J. Lu" <hjl.tools@gmail.com> wrote:
>
>
> >> OK witht that change.
> >> Honza
> >
> >I am checking in this patch with the updated comments:
> >
> > /* Disable indirect call profiling for an IFUNC resolver and its
> > callees since it requires TLS which hasn't been set up yet when
> > the dynamic linker is resolving IFUNC symbols. See
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114115
> > */
> >
> >Thanks.
> >
>
> + /* Skip if it has been visited. */
> + unsigned int uid = e->caller->get_uid ();
> + if (bitmap_bit_p (ifunc_ref_map, uid))
> + continue;
> + bitmap_set_bit (ifunc_ref_map, uid);
>
> I think you could have written this as
> if (!bitmap_set_bit (ifunc_ref_map, uid))
> continue;
>
Feel free to submit a patch.
Thanks.
--
H.J.
next prev parent reply other threads:[~2024-04-05 1:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 12:40 H.J. Lu
2024-04-03 13:38 ` Jan Hubicka
2024-04-03 13:49 ` H.J. Lu
2024-04-05 0:34 ` rep.dot.nop
2024-04-05 1:03 ` H.J. Lu [this message]
2024-04-05 7:02 ` rep.dot.nop
2024-04-03 15:31 ` Peter Bergner
2024-04-03 15:44 ` H.J. Lu
2024-04-03 15:45 ` Andrew Pinski
2024-04-03 16:16 ` Peter Bergner
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=CAMe9rOof8vABTYU33mogvAEzaOmzaTihApUu3wdONiNmw_K0hA@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=rep.dot.nop@gmail.com \
/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).