[cfe-dev] Clang defects that were fixed but still show up as Open
Matheus Izvekov via cfe-dev
cfe-dev at lists.llvm.org
Sun Jul 4 09:20:09 PDT 2021
I think it's completely fine to go in and close bugs that have been
dormant for a long time if you cannot reproduce them anymore.
I don't think there is anyone in the community that is really keeping
tabs on all the open bugs in clang,
so I don't think you would be stepping on anyone else's toes here and
would not need to coordinate it or anything.
Either testing existing cases from the bug description, or new ones
and linking to compiler explorer (but please also paste the code used
in case the link ever goes down).
As someone who often trawls for open bugs, I would highly appreciate this!
On Fri, Jul 2, 2021 at 10:58 AM Chirca, Valentin-Catalin (Valentin)
via cfe-dev <cfe-dev at lists.llvm.org> wrote:
> Hi everyone,
> My name is Valentin Chirca and I am a compiler engineer at Wind River.
> We have been working on classifying clang defects for functional safety lately. While doing this we found some clang defects that appear to be fixed but are not marked so in Bugzilla. We would like to mark those defects as Resolved-Fixed, with a link to https://godbolt.org/ showing that the issue is no longer reproducible. Would that be ok or is there anything else that needs to be done for those cases?
> Here is another question: Should we wait for the migration from Bugzilla to GitHub Issues to happen or is it ok to make these updates in Bugzilla now?
> cfe-dev mailing list
> cfe-dev at lists.llvm.org
More information about the cfe-dev