public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin O'Connor <kevin@koconnor.net>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: kvm-devel@lists.sourceforge.net, Avi Kivity <avi@qumranet.com>
Subject: Re: [ANN] Bochs bios ported to gcc
Date: Mon, 7 Apr 2008 09:05:45 -0400	[thread overview]
Message-ID: <20080407130545.GA22933@ohio.lan> (raw)
In-Reply-To: <47F9C243.2060803@zytor.com>

On Sun, Apr 06, 2008 at 11:42:11PM -0700, H. Peter Anvin wrote:
> bcc is truly horrible.  gcc is, of course, best, although it does produce 
> bloated 16-bit code.

With gcc, the text size has actually been significantly reduced - I'm
not sure if this is because I'm using -fwhole-program and -Os or if it
is just the result of bcc being so bad.

The biggest problem I've run into is stack usage on the 16-bit bios
calls.

>For "proper" 16-bit code, OpenWatcom is currently the 
> best open source compiler, and it's actually getting usable even on a Linux 
> host.

One of the developers on the bochs list also recommended OpenWatcom.

The bios currently has quite a bit of 32bit code in addition to the
16bit code.  It's very convenient to be able to compile the same code
in both modes (eg, printf, inb, etc.).  I'd need to move both 32bit
and 16bit code to OpenWatcom to do this.

-Kevin

-------------------------------------------------------------------------
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

  reply	other threads:[~2008-04-07 13:05 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
2008-04-07 13:05     ` Kevin O'Connor [this message]
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=20080407130545.GA22933@ohio.lan \
    --to=kevin@koconnor.net \
    --cc=avi@qumranet.com \
    --cc=hpa@zytor.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox