On Mon, Mar 19, 2007 at 07:23:43AM -0700, Darrin Chandler wrote: > On Mon, Mar 19, 2007 at 01:53:00PM +0100, Karel Kulhavy wrote: > > It's therefore not the responsibility of the programmer to check whether the > > result of optimization is correct. Therefore it's not the optimizations that > > are source of bugs, but bugs in GCC. > > But if you write a program and the user finds it full of bugs, are they > going to care that you can say that it's GCC's fault? The burden falls
When I write a program then I specify the language - say ISO/IEC 9899:1999. If the compiler is buggy then it doesn't conform to ISO/IEC 9899:1999 - the compiled program behaviour breaches the ISO/IEC 9899:1999 spec. Then it's the user's problem that he compiled with a compiler that doesn't meet requirements I clearly stated. CL< > on the developers to make code that works, including working around > problems in the compiler. Sad, but true. > > -- > Darrin Chandler | Phoenix BSD Users Group > [EMAIL PROTECTED] | http://bsd.phoenix.az.us/ > http://www.stilyagin.com/darrin/ |
