From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: James Hilliard <james.hilliard1@gmail.com>,
Romain Naour <romain.naour@gmail.com>,
Giulio Benetti <giulio.benetti@benettiengineering.com>,
"Yann E. MORIN" <yann.morin.1998@free.fr>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/gcc: ensure __register_frame is optimized out for glibc
Date: Fri, 25 Nov 2022 15:15:26 +0100 [thread overview]
Message-ID: <20221125151526.37a4a872@windsurf> (raw)
In-Reply-To: <620448da-4dda-3d9d-cb39-5c8a278767d6@mind.be>
On Fri, 25 Nov 2022 15:06:21 +0100
Arnout Vandecappelle <arnout@mind.be> wrote:
> James previously already reported the problem to glibc:
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=29621
>
> I picked up the thread in both issues, I was able to narrow the problem down a
> little more, but in the end the conclusion seems to be "We can't support that on
> the glibc side at present."
>
> So I applied this patch to master, after making two major changes:
>
> - move it to host-gcc-initial only;
> - instead of putting the full condition in the .mk file, make a Config.in symbol
> BR2_TOOLCHAIN_HAS_GCC_BUG_107728.
>
> ... And now I notice I forgot to put the changes I made in the commit message.
> But it's pushed already.
>
> Anyway, applied to master, thanks!
Thanks for following up on this. I reviewed the change you pushed, and
it looks like the best trade-off. Thanks again!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-11-25 14:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 22:38 [Buildroot] [PATCH 1/1] package/gcc: ensure __register_frame is optimized out for glibc James Hilliard
2022-10-30 8:30 ` Yann E. MORIN
2022-11-17 7:53 ` Thomas Petazzoni via buildroot
2022-11-25 14:06 ` Arnout Vandecappelle
2022-11-25 14:15 ` Thomas Petazzoni via buildroot [this message]
2022-12-06 22:03 ` Peter Korsgaard
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=20221125151526.37a4a872@windsurf \
--to=buildroot@buildroot.org \
--cc=arnout@mind.be \
--cc=giulio.benetti@benettiengineering.com \
--cc=james.hilliard1@gmail.com \
--cc=romain.naour@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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