On Thu, Apr 26, 2007 at 10:27:47PM -0700, H. Peter Anvin wrote: >Eric W. Biederman wrote: >> "H. Peter Anvin" <[EMAIL PROTECTED]> writes: >> >>> A lot of that code (although, of course, not all) could be written in C, >>> though. I'm thinking of taking a stab at rewriting it that way. >> >> Is this using the .code16gcc? Or are you thinking of some other >> technique. Requiring another C compiler to build the kernel would >> be a pain to use. > >.code16gcc was what I was using. There is a GSoC project that I'm >mentoring to get 16-bit support for gcc, that will be possible to >eventually migrate to (for code size) if/when it gets implemented and >gets pushed out far enough, but that's for the future. > > -hpa
Thanks! I will take a look at that file. Maybe we can rewrite them in C, use a 16-bit C compiler to generate AT&T asm code and finally push the asm code in the kernel source tree. But perhaps there is no such ideal compiler. ;) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
