we have a great community of users and testers who take time to file bugs for various issues like crashes and miscompiles. That’s a valuable source of information for the project, but I think we aren’t making the most out of it.
Unfortunately it can take quite a long time from filing an issue to it being acknowledged and fixed. For example, LLVM/Clang contains a number of known miscompiles that can stay in the codebase for years.
Over the last couple of weeks I tried to work through many reported miscompiles and crashes to bring the information in the issue tracker more up-to-date and I am sharing his post to hopefully get more people interested. While working on fixing bugs might not be as exciting as working on new features, fixing some of these bugs will have a big positive impact on our users’ experience. If you are interested in helping out, there are multiple things you could do:
- Update information in the issue tracker:
(One challenge is that we have a number of bugs that have been reported years ago, but never had any further comments.)
- Try to reproduce reported issues,
- tag them with appropriate labels,
- possible attach a minimal IR reproducer.
- Pick one or more issues and try to fix them.
- Keep testing and filing issue for LLVM, we will eventually get to them
To wrap up, here are links to the lists of known miscompiles & crashes in Clang/LLVM, with the number of open bugs as of today. I may share infrequent updates as we hopefully make progress on squashing some of those!
- Known Miscompiles (87 open April 12)
- Known Clang crashes (46 open April 12)
- LLVM crashes (47 as of April 12)