From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu From: "AMSRL-CI-CN" Message-ID: References: Subject: Re: [9fans] GUI toolkit for Plan 9 Date: Thu, 28 Feb 2002 14:55:46 +0000 Topicbox-Message-UUID: 5bc8a77a-eaca-11e9-9e20-41e7f4b1d025 wrote in message news:ce0ce59eb0d583584480f57dde2bd1a2@plan9.bell-labs.com... > ... However, it seems to be an > accepted consequence amongst compiler writers to trade off > possible incorrect code generation against probable speed > gains. The compiler developers I know don't accept that trade-off. However, C is unique in that there are many "fuzzy" areas of the language where determining what is and is not permitted by the compiler is difficult. That's because of C's heritage as a systems implementation language and the associated desire to permit as much optimization as feasible without making the language untrustworthy when used competently. The current rules for C allow a lot of optimization, but there are also rules for programming so as to not be bitten by the optimizations. It is certainly true that some over-zealous compiler hackers have introduced bugs from time to time. But these are generally acknowledged to be bugs and are fixed when they turn up.