A list of bugs that I’ve filed and their current status. This list is not complete but I’ll try to remember to add new bugs here. It’s interesting to see the track record of various projects in terms of their willingness/ability to fix bugs.
Eclipse. 2019-03-05. Pending.
Gcc. 2017-05-30. Pending.
Confirmed as a bug only after several months, even though test case was provided…
LLVM. 2015-09-18. Pending.
3 years with no response.
GNU libtool (version 2.4.6). 2015-06-25. Pending, but I’m not sure this is a bug in libtool anymore.
Sent by email to firstname.lastname@example.org:
I have discovered what I believe is a bug in libtool: It does not pass the “-fno-strict-aliasing” compilation flag to the link stage. This is not normally a problem, but is certainly a problem is “-flto” (link time optimization) is used. In this case code that works correct only without strict aliasing will incorrectly after being linked.
If you need any further information, please don’t hesitate to ask.
(build problem with workaround available) No meaningful response after 4 years.
Resolved (or otherwise closed):
Eclipse. 2018-9-14. Fixed within days of being reported!
Eclipse. 2017-12-29. Fixed (I fixed it and the patch was merged).
Gcc. 2017-07-22. Resolved (duplicate).
Cairo. 2017-03-08. Resolved (invalid).
9 months with no response. I eventually prompted on IRC and with help of a developer realised that the bug was invalid (and the patch that was submitted with it was wrong). Alarmingly, the bugzilla admin has “not been seen in a while“.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30527 Addressed but still marked “Uncomfirmed” (after 5 years…)
Java JDK. 2014-05-13
https://bugs.openjdk.java.net/browse/JDK-8043315 Fixed. (3 years after filed. Fix is now available in early access builds of JDK 10).
Firefox 7/June/16 – possibly bogus.
Gcc. 2017-04-29. Fixed.
Ruby on Rails.
https://github.com/rails/rails/issues/16291 Closed without resolution.
http://bugs.mysql.com/48284 Fixed (filed with solution).