From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Jörg Sommer" <joerg.sommer@navimatix.de>
Cc: Thomas Perrot <thomas.perrot@bootlin.com>,
openembedded-core@lists.openembedded.org,
changqing.li@windriver.com, rs@ti.com,
ricardo.salveti@oss.qualcomm.com, raj.khem@gmail.com,
antonin.godard@bootlin.com
Subject: Re: [OE-core] [PATCH] lto.inc: add DEBUG_PREFIX_MAP back to TARGET_LDFLAGS
Date: Mon, 30 Mar 2026 11:50:14 +0100 [thread overview]
Message-ID: <d1c47a43e10b398376ff27a65dd1be14313a5c94.camel@linuxfoundation.org> (raw)
In-Reply-To: <acpOozTnDECIDOVg@navimatix.de>
On Mon, 2026-03-30 at 12:23 +0200, Jörg Sommer wrote:
> Richard Purdie schrieb am Mo 30. Mär, 11:18 (+0100):
> > On Mon, 2026-03-30 at 11:59 +0200, Thomas Perrot wrote:
> > > On Sat, 2026-03-28 at 21:26 +0100, Jörg Sommer via
> > > lists.openembedded.org wrote:
> > > > Changqing Li via lists.openembedded.org schrieb am Mi 04. Feb,
> > >
> > > I confirm this patch is required to fix QA check build paths for a
> > > few packages.
> >
> > Can someone please work out a smaller reproducer to provide to upstream
> > gcc/binutils so we can try and get the underlying bug fixed?
>
> I've send some simple test cases in
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=124581
Thanks, I've tried to raise awareness in the other bug.
Cheers,
Richard
prev parent reply other threads:[~2026-03-30 10:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 5:26 [PATCH] lto.inc: add DEBUG_PREFIX_MAP back to TARGET_LDFLAGS changqing.li
2026-02-04 9:34 ` Richard Purdie
2026-02-04 18:17 ` Ricardo de Araujo (Salveti)
2026-02-04 22:34 ` Richard Purdie
2026-03-28 20:26 ` [OE-core] " Jörg Sommer
2026-03-30 9:59 ` Thomas Perrot
2026-03-30 10:18 ` Richard Purdie
2026-03-30 10:23 ` Jörg Sommer
2026-03-30 10:50 ` Richard Purdie [this message]
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=d1c47a43e10b398376ff27a65dd1be14313a5c94.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=antonin.godard@bootlin.com \
--cc=changqing.li@windriver.com \
--cc=joerg.sommer@navimatix.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=ricardo.salveti@oss.qualcomm.com \
--cc=rs@ti.com \
--cc=thomas.perrot@bootlin.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