On Fri, Sep 13, 2024 at 5:17 PM Jakub Kicinski <kuba@xxxxxxxxxx> wrote: > > On Fri, 13 Sep 2024 15:20:13 -0700 Mina Almasry wrote: > > I have not reported the issue to GCC yet. From the build break thread > > it seemed a fix was urgent, so I posted the fix and was planning to > > report the issue after. If not, no problem, I'll report the issue and > > repost the fix with a GCC bugzilla link, waiting 24hr before reposts > > this time. > > I should have clarified, the "please post ASAP" applies > to all devmem build fixes, ignore the cool down period :) > > > I just need to go through the steps in https://gcc.gnu.org/bugs/, > > shouldn't be an issue. > > Just post the link here, I'll add it to the commit msg when applying. Ah, I need a GCC bugzilla account before I can file bugs there. I don't currently have one and creating an account involves emailing them and waiting 24hr. I've done that and am waiting for an account. I'll file the issue as soon as I get access and post the link here. I'm also poking to see if anyone around already has an account and can file the issue on my behalf. -- Thanks, Mina
