From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Frager, Neal" <neal.frager@amd.com>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>,
"joseph@anodize.com" <joseph@anodize.com>,
"ramin.moussavi@yacoub.de" <ramin.moussavi@yacoub.de>,
"thesamprice@gmail.com" <thesamprice@gmail.com>,
"ju.o@free.fr" <ju.o@free.fr>,
"arnout@rnout.be" <arnout@rnout.be>,
"lordrasmus@gmail.com" <lordrasmus@gmail.com>,
"romain.naour@smile.fr" <romain.naour@smile.fr>,
"Simek, Michal" <michal.simek@amd.com>,
"romain.naour@gmail.com" <romain.naour@gmail.com>
Subject: Re: [Buildroot] [PATCH v2 1/1] package/gcc: add microblaze frame unwinding fix to v15 and v16
Date: Sun, 11 Oct 2026 08:48:09 +0200 [thread overview]
Message-ID: <assxFoQCpRtNjAkx@windsurf> (raw)
In-Reply-To: <BL1PR12MB5032C1DBCFDE52533D8A1BE2F0902@BL1PR12MB5032.namprd12.prod.outlook.com>
On Sun, Oct 11, 2026 at 04:51:56AM +0000, Frager, Neal via buildroot wrote:
> > Applied to master, thanks. What about gcc 14.x? The issue didn't exist?
>
> I believe gcc 14.x needs this patch too. I just never tested gcc 14.x.
So, will you send a patch for GCC 14.x ? :-)
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
prev parent reply other threads:[~2026-10-11 6:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 4:01 [Buildroot] [PATCH v2 1/1] package/gcc: add microblaze frame unwinding fix to v15 and v16 Neal Frager via buildroot
2026-10-10 21:10 ` Thomas Petazzoni via buildroot
2026-10-11 4:51 ` Frager, Neal via buildroot
2026-10-11 6:48 ` Thomas Petazzoni via buildroot [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=assxFoQCpRtNjAkx@windsurf \
--to=buildroot@buildroot.org \
--cc=arnout@rnout.be \
--cc=joseph@anodize.com \
--cc=ju.o@free.fr \
--cc=lordrasmus@gmail.com \
--cc=michal.simek@amd.com \
--cc=neal.frager@amd.com \
--cc=ramin.moussavi@yacoub.de \
--cc=romain.naour@gmail.com \
--cc=romain.naour@smile.fr \
--cc=thesamprice@gmail.com \
--cc=thomas.petazzoni@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