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. > 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. You compare the test results of your patched gcc to the test results of an unpatched gcc. How did you get lost? To "compile gcc 3 times" you just run "make", and it does that automatically (unless you configured with --disable-bootstrap, in which case it just compiles once). > 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. > No change ever takes two minutes, because you have to write tests at a minimum.
