From: Peter Korsgaard <peter@korsgaard.com>
To: "Frager, Neal via buildroot" <buildroot@buildroot.org>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
"Frager, Neal" <neal.frager@amd.com>,
"romain.naour@gmail.com" <romain.naour@gmail.com>,
"giulio.benetti@benettiengineering.com"
<giulio.benetti@benettiengineering.com>,
"ju.o@free.fr" <ju.o@free.fr>
Subject: Re: [Buildroot] [PATCH v1 1/1] package/gcc: add microblaze atomic support
Date: Mon, 11 Aug 2025 11:22:59 +0200 [thread overview]
Message-ID: <87jz3anrf0.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <SA1PR12MB5615BF7BD79B49730E8E7CE8F028A@SA1PR12MB5615.namprd12.prod.outlook.com> (Neal via buildroot Frager's message of "Mon, 11 Aug 2025 08:33:48 +0000")
>>>>> "Frager," == Frager, Neal via buildroot <buildroot@buildroot.org> writes:
> [AMD Official Use Only - AMD Internal Distribution Only]
> Hi Thomas,
>> You guys are amazing!
>>
>> I was planning to start working on this today, but you have not only already
>> created a work around, but have basically shared everything the gcc team
>> should need to fix the issue correctly.
>> Well, not yet. They are still waiting for me to share the irq.i
>> before/after the problematic GCC commit. So we have for now pointed at
>> the issue, but not actually provided enough information to fix it.
> Ok sure, but the hard part is done already. You have narrowed the issue down
> to a single c file which by chance is fairly short.
> If one of them wanted to, they could create the irq.i files and handle the
> rest.
> I am still impressed! Great work!
Committed, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-08-11 9:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 4:51 [Buildroot] [PATCH v1 1/1] package/gcc: add microblaze atomic support Neal Frager via buildroot
2025-08-04 19:40 ` Thomas Petazzoni via buildroot
2025-08-05 7:29 ` Frager, Neal via buildroot
2025-08-05 8:09 ` Thomas Petazzoni via buildroot
2025-08-05 10:31 ` Frager, Neal via buildroot
2025-08-05 10:58 ` Thomas Petazzoni via buildroot
2025-08-06 20:17 ` Thomas Petazzoni via buildroot
2025-08-07 4:49 ` Frager, Neal via buildroot
2025-08-11 7:31 ` Frager, Neal via buildroot
2025-08-11 8:12 ` Thomas Petazzoni via buildroot
2025-08-11 8:33 ` Frager, Neal via buildroot
2025-08-11 9:22 ` Peter Korsgaard [this message]
2025-08-21 19:20 ` Thomas Perale via buildroot
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=87jz3anrf0.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=ju.o@free.fr \
--cc=neal.frager@amd.com \
--cc=romain.naour@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