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.
Still pending:
Tianocore (EDK 2). 2021-07-18. Pending.
https://bugzilla.tianocore.org/show_bug.cgi?id=3495
Confirmed as a bug, but not fixed, despite it being a one-line fix that I’ve pointed out.
LLVM. 2015-09-18. Pending.
https://llvm.org/bugs/show_bug.cgi?id=24875
Now at: https://github.com/llvm/llvm-project/issues/25249
7 years with no response; issue appears to have been resolved in the meantime.
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 bug-libtool@gnu.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.
Now filed: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=20899
Thunderbird. 2015-01-25.
https://bugzilla.mozilla.org/show_bug.cgi?id=1125599 Pending.
(build problem with workaround available) No meaningful response after 7 years and counting.
Resolved (or otherwise closed):
Eclipse. 2019-03-05. Pending.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=545040
I ended up filing a patch which was accepted.
Pango. 2017-03-07. Closed.
https://bugzilla.gnome.org/show_bug.cgi?id=779748
Now at: https://gitlab.gnome.org/GNOME/pango/issues/271
Closed circa 2019 because “we’ve switched to meson as our build system”. No mention of whether the underlying issue has been resolved.
Gcc. 2017-05-30. Resolved.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80916
Confirmed as a bug only after several months, even though test case was provided. Fixed in 2019.
Eclipse. 2018-9-14. Fixed within days of being reported!
https://bugs.eclipse.org/bugs/show_bug.cgi?id=539076
Eclipse. 2017-12-29. Fixed (I fixed it and the patch was merged).
https://bugs.eclipse.org/bugs/show_bug.cgi?id=529299
Gcc. 2017-07-22. Resolved (duplicate).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81516
Cairo. 2017-03-08. Resolved (invalid).
https://bugs.freedesktop.org/show_bug.cgi?id=100119
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“.
GCC. 2007-01-21
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30527 Addressed but still marked “Unconfirmed” (after 15 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.
https://bugzilla.mozilla.org/show_bug.cgi?id=1278674
Gcc. 2017-04-29. Fixed.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80569
Ruby on Rails.
https://github.com/rails/rails/issues/16291 Closed without resolution.
Compiz.
https://bugs.launchpad.net/compiz/+bug/1392715 Fixed.
Mysql.
http://bugs.mysql.com/48284 Fixed (filed with solution).
Software is Crap 