Ports and gcc
Now that Matthias is on holiday, I'm trying to put in my bit with gcc again.
I've been going over the bugs
and have been retitling arch-specific ones.
I'd appreciate it very much if the porters could go over these bugs once
again. Real gcc bugs typically need to be forwarded upstream, and the
chances of upstream responses increase greatly if bugs are detailed:
- they contain a minimal example showing the problem (use #if 0 .. #endif
to divide and conquer) and
- they show exactly which optimisations (-O* -f* -fno*) trigger the problem
(rather than simply -On).
I realise it's a lot of work to figure this out, but it definitely increases
chances the problems get fixed.
LEADERSHIP A form of self-preservation exhibited by people with auto-
destructive imaginations in order to ensure that when it comes to the crunch
it'll be someone else's bones which go crack and not their own.
- The Hipcrime Vocab by Chad C. Mulligan