Betrayed by a bitfield
Feb 11, 2012, 14:00 (1 Talkback[s])
(Other stories by Jonathan Corbet)
"Developers tend to fear compiler bugs, and for good reason:
such bugs can be hard to find and hard to work around. They can
leave traps in a compiled program that spring on users at bad
times. Things can get even worse if one person's compiler bug is
seen by the compiler's developer as a feature - such issues have a
tendency to never get fixed. It is possible that just this kind of
feature has turned up in GCC, with unknown impact on the
kernel.
Complete Story
Related Stories:
- The FOR looping statement. A semantic compiler plugin(Jan 14, 2012)
- Adding support for if, while, and do while, to a simple compiler and virtual machine written in Php(Jan 09, 2012)
- A Linux Compiler Deathmatch: GCC, LLVM, DragonEgg, Open64, Etc...(Feb 01, 2011)
- Benchmarks Of GCC 4.5.0 Compiler Performance(Apr 19, 2010)
- 8 of the Best Free Linux Compilers(Aug 04, 2009)
- GCC 4.4 improves open source compiler with Graphite(Apr 29, 2009)
- Cross compilers, the new wave(Apr 15, 2009)
- Cross Compiler Blues(Jan 01, 2008)
