On Sat, 9 May 2020 at 19:56, John Paul Adrian Glaubitz <glaub...@physik.fu-berlin.de> wrote: > > On 5/9/20 12:31 PM, Arseny Solokha wrote: > > I'd also like to nominate the following two: > > > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52927 > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60158 > > > > which I also cannot close myself. There won't be any further revisions of > > this > > list by me. > > They affect given older versions, so if you just close them, that would imply > that the bug in question in gcc-4.5.3 has been dealt with - which I assume > is not the case.
Did you bother to read my reply? Closing a bug means no more work will be done, not that work has already been done. > So, again, I'm not sure what you gain by closing these bugs. Having them > marked > as open means that someone has observed the issue with a certain gcc version > and target. Please read my first email to you. > Moving it to "closed" just expresses that some people don't care about this > bug anymore. But it doesn't change the fact that the bug still exists. Please read my first email to you. > The only thing you gain by closing such bugs is that you are reducing the > number of open bug reports and you can somehow claim you fixed a bug. No, it doesn't claim anything was fixed, please read my first email to you.
