From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 25 Apr 2006 22:11:49 -0700 From: Roman Shaposhnick To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Subject: Re: [9fans] impressive Message-ID: <20060426051149.GD20561@submarine> References: <3e1162e60604252157m50da62dardb98759d7c4152da@mail.gmail.com> <444EFCCF.8040507@lanl.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <444EFCCF.8040507@lanl.gov> User-Agent: Mutt/1.4.1i Topicbox-Message-UUID: 46632c82-ead1-11e9-9d60-3106f5b1d025 On Tue, Apr 25, 2006 at 10:53:35PM -0600, Ronald G Minnich wrote: > David Leimbach wrote: > >The main reason that intel and other C compilers implement gcc > >extensions is because there is a lot of software that relies on them, > >like the linux kernel for instance. > > Yes, the standard question asked here when a company comes in with a > whiz-bang C compiler is 'can you build a bootable the linux kernel'. The > initial answer is always "no". It in the usual case remains "no". For > those companies that care (there are not many -- in fact there is only > one I can think of) We (myself included) are trying to make it two ;-) http://developers.sun.com/sunstudio/linux > it takes several years before the answer is "yes". The real problem is that its not just gcc compatibility, but rather gccX.Y compatibility. These guys are wild when it come to things like __asm__ specificators and such. In fact, Intel's dude I met at SC05 was really proud that their compiler is more compatible with gcc than gcc itself. After all, icc has a gcc ABI switch ;-) Thanks, Roman.