From: WANG Cong <xiyou.wangcong@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Michael McConnell <soruk@eridani.co.uk>,
linux-kernel@vger.kernel.org, Andi Kleen <ak@suse.de>
Subject: Re: MAINTAINERS file out of date?
Date: Fri, 27 Apr 2007 18:28:35 +0800 [thread overview]
Message-ID: <20070427102835.GA11449@localhost.localdomain> (raw)
In-Reply-To: <463189D3.3070805@zytor.com>
On Thu, Apr 26, 2007 at 10:27:47PM -0700, H. Peter Anvin wrote:
>Eric W. Biederman wrote:
>> "H. Peter Anvin" <hpa@zytor.com> 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. ;)
next prev parent reply other threads:[~2007-04-27 10:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 22:19 MAINTAINERS file out of date? Michael McConnell
2007-04-26 23:13 ` H. Peter Anvin
2007-04-27 1:09 ` WANG Cong
2007-04-27 1:12 ` H. Peter Anvin
2007-04-27 2:32 ` WANG Cong
2007-04-27 4:22 ` Eric W. Biederman
2007-04-27 5:16 ` H. Peter Anvin
2007-04-27 5:24 ` Eric W. Biederman
2007-04-27 5:27 ` H. Peter Anvin
2007-04-27 10:28 ` WANG Cong [this message]
2007-04-27 15:55 ` H. Peter Anvin
2007-04-27 10:34 ` Andi Kleen
2007-04-27 15:56 ` H. Peter Anvin
2007-04-27 17:02 ` Eric W. Biederman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070427102835.GA11449@localhost.localdomain \
--to=xiyou.wangcong@gmail.com \
--cc=ak@suse.de \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=soruk@eridani.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox