3 ms·
"someone like Walter Bright will have to jump in, he probably knows GCC inside-out" FWIW, walter has not contributed a single patch to GCC i can find in the pa
by DannyBee 11y ago
"someone like Walter Bright will have to jump in, he probably knows GCC inside-out"
FWIW, walter has not contributed a single patch to GCC i can find in the past 10 years (It may be longer, i stopped looking) :)
Not that this makes him bad in any way, mind you, he's just not who i'd go to for gcc expertise. That would be someone like Richard Henderson, who is pretty much never talked about, but has touched pretty much all parts of the compiler and always does great work.
Also note that embedded developers in general do not have a good reputation among compiler people for doing "sound work". Again, not that this is a characterization of their engineering skills - They often have very tight deadlines, so the amount of time they can spend figuring out things instead of applying bandaids tends to be pretty limited. So they patch something, submit it, and move on.
- bionsuba 11y ago"walter has not contributed a single patch to GCC i can find in the past 10 years (It may be longer, i stopped looking) :)" It's worse than that. Because LLVM and GCC are copy-lefted and his compiler has a proprietary backend, he forces himself not to even look at their code in order to make the lawyers happy.
- comex 11y ago(LLVM is under a BSD-style license and thus not copylefted, although it does require attribution.)
- WalterBright 11y agoHaha, I once got sued by a company claiming I stole code from them, and their lawyer got sent packing when it turned out they had stolen the code from me. (I had a registered copyright on it.) One thing I absolutely adore about Github is the audit trail about who contributed what and when. It's a solid gold defense, and a way to limit the damage if someone does check in bad code.
- WalterBright 11y agoNo, I've never contributed a patch to GCC. No need to look :-)