All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Avi Kivity <avi@qumranet.com>
Cc: kvm-devel@lists.sourceforge.net, Kevin O'Connor <kevin@koconnor.net>
Subject: Re: [ANN] Bochs bios ported to gcc
Date: Sun, 06 Apr 2008 23:42:11 -0700	[thread overview]
Message-ID: <47F9C243.2060803@zytor.com> (raw)
In-Reply-To: <47F8BC77.3060106@qumranet.com>

Avi Kivity wrote:
> Kevin O'Connor wrote:
>> I have been working on a port of bochs bios to gcc.  This port is
>> nearly complete.  The new code does not rely on bcc or dev86.
>> Instead, it uses standard gcc and gas.  It should compile on any
>> recent Linux distribution.
>>
>> I'm sending this email because I understand kvm has a copy of bochs
>> bios in its repository.
>>   
> 
> While moving away from the horror that is bcc is a blessing, the way to 
> really benefit from it is to have this code replace the original bochs 
> bios.  This way updates to the bochs bios are not lost for anyone using 
> the new code.
> 
> Have you proposed replacing the bios to the bochs developers?  What was 
> the reaction?
> 

bcc is truly horrible.  gcc is, of course, best, although it does 
produce bloated 16-bit code.  For "proper" 16-bit code, OpenWatcom is 
currently the best open source compiler, and it's actually getting 
usable even on a Linux host.

	-hpa

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Register now and save $200. Hurry, offer ends at 11:59 p.m., 
Monday, April 7! Use priority code J8TLD2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

  parent reply	other threads:[~2008-04-07  6:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-02  1:42 [ANN] Bochs bios ported to gcc Kevin O'Connor
2008-04-06 12:05 ` Avi Kivity
2008-04-06 15:03   ` Kevin O'Connor
2008-04-07  6:42   ` H. Peter Anvin [this message]
2008-04-07 13:05     ` Kevin O'Connor
2008-04-07 16:18       ` H. Peter Anvin

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=47F9C243.2060803@zytor.com \
    --to=hpa@zytor.com \
    --cc=avi@qumranet.com \
    --cc=kevin@koconnor.net \
    --cc=kvm-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.