From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Romain Naour <romain.naour@gmail.com>,
James Hilliard <james.hilliard1@gmail.com>,
Giulio Benetti <giulio.benetti@benettiengineering.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/gcc: ensure __register_frame is optimized out for glibc
Date: Thu, 17 Nov 2022 08:53:39 +0100 [thread overview]
Message-ID: <20221117085339.4a4d5d8f@windsurf> (raw)
In-Reply-To: <20221030083033.GC1058960@scaer>
On Sun, 30 Oct 2022 09:30:33 +0100
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> Should this not be limitied to the intial compiler only? Otherwise, why
> would we need it for the final compiler?
I confirm limiting the work-around to gcc-initial works.
However, I have reported the bug to gcc upstream, and they say the
issue is in glibc:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107728
To be honest, even after reading multiple times the feedback from the
gcc folks, I'm not entirely sure that I really understand their
explanation nor how to move forward with investigating the issue.
Best regards,
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-17 7:53 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 [this message]
2022-11-25 14:06 ` Arnout Vandecappelle
2022-11-25 14:15 ` Thomas Petazzoni via buildroot
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=20221117085339.4a4d5d8f@windsurf \
--to=buildroot@buildroot.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.