On Mon, Jul 14, 2025 at 1:16 PM Uros Bizjak <ubiz...@gmail.com> wrote:
>
> On Sun, Jul 13, 2025 at 12:16 AM Sam James <s...@gentoo.org> wrote:
> >
> > "H.J. Lu" <hjl.to...@gmail.com> writes:
> >
> > > On Sat, Jul 12, 2025 at 6:58 AM Siddhesh Poyarekar <siddh...@gotplt.org>
> > > wrote:
> > >>
> > >> On 2025-07-11 15:28, Uros Bizjak wrote:
> > >> >> Why not just switch over unconditionally? __fentry__ seems like a
> > >> >> better alternative to mcount overall and it has been around long
> > >> >> enough
> > >> >> that even older deployments should be relatively unaffected.
> > >> >
> > >> > Actually, it is switched on by default for i?86-*-linux* |
> > >> > x86_64-*-linux*. The default for --enable-x86-64-mfentry is "auto",
> > >> > which triggers the mentioned condition. One still has a chance to use
> > >> > "yes" or "no" in addition to "auto" when configuring with
> > >> > --{enable|disable}-x86-64-mfentry.
> > >>
> > >> Oh that's good then.
> > >>
> > >> Thanks,
> > >> Sid
> > >
> > > Here is the v2 patch. The differences are
> > >
> > > 1. Enable -mfentry by default for i?86-*-*gnu* | x86_64-*-*gnu*,
> > > not i?86-*-*linux* | x86_64-*-*linux*.
> > > 2. Adjust some testcases.
> > >
> > > OK for master?
> >
> > I'll test it tonight but it looks good to me now. Thanks.
>
> Assuming that tests passed, OK for mainline.
HJ, please also mention this change in gcc-16 release notes.
Thanks,
Uros.
