Request easy bug fix
Hi, I hope it is not inappropriate to call attention to a specific bug. https://gcc.gnu.org/bugzilla//show_bug.cgi?id=85487. I tried to do it myself, but got lost on the part where I needed to compile gcc 3 times and compare test results to some (un)known test results. It was too much time and setup for a fix that will probably take 2 minutes to implement, so I am asking if someone that already contributes to gcc can please look at this. I think it should only take a couple of minutes to implement. Thank you
Fwd: Request easy bug fix
On Tue, Feb 15, 2022 at 5:20 PM Jonathan Wakely wrote: > > > On Tue, 15 Feb 2022 at 13:58, David Malcolm wrote: > >> On Tue, 2022-02-15 at 12:55 +, Jonathan Wakely via Gcc wrote: >> > On Tue, 15 Feb 2022 at 12:34, Baruch Burstein via Gcc < >> > gcc@gcc.gnu.org> >> > wrote: >> > >> > > Hi, >> > > >> > > I hope it is not inappropriate to call attention to a specific bug. >> > > https://gcc.gnu.org/bugzilla//show_bug.cgi?id=85487. > > > Clang and the MSVC compiler both ignore any tokens after the pragma, so > that seems good enough for GCC too: > > https://godbolt.org/z/norv947a5 > > I am sorry for posting this again, but to the best of my understanding of the thread at https://gcc.gnu.org/bugzilla//show_bug.cgi?id=85487, the patch already exists (I am not sure where), and was not merged to GCC 12 only because I called attention to it too late in the dev cycle, so I am trying to get this in earlier for GCC 13. It is literally a "do-nothing" patch.
Re: Request easy bug fix
On Mon, Oct 31, 2022 at 4:03 PM Jonathan Wakely wrote: > > You've waited until two weeks before the deadline for GCC 13 changes! > I'll re-propose my patch, but it would have been much better to do it > when I wasn't rushing to get 20 *other* changes finished in the next > two weeks! Thank you, and I apologize. I was hoping it gets in without me having to point attention to it since I thought that would be impolite. If it doesn't get in, I now know to ask again in May.
