[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] Mac OS X issues

From: Mike Kronenberg
Subject: Re: [Qemu-devel] Mac OS X issues
Date: Sun, 11 Dec 2005 18:22:43 +0100

Your the man!

gcc4 and -fno-tree-ch did the trick for me, too.
-fno-tree-ch was mentioned earlyer on this list, to compile with gcc4 on OS X. But since gcc4 is still not in the default toolchain, I did not even try :(.

Seams that we have a problem with gcc3.3 and not gcc4 for once :)

The error behavement is similar on your machine. I also got bus error (Sometimes it did not reach the menu, too. I started to hit the 3 very early, so I could go right thru it... Early crashes always happened for me on MS-DOS 6.22 and DOS 7.

Tested it with DOS 6.22 and DOS 7 (win95). No Problems so far.

I hope Fabrice stumbles upon this.

Maybe we should make the Patch a little more selective with "ifeq ($ (CONFIG_DARWIN),yes)" and post it.
Don't know whether this affects other Platforms, too...

Thanks for Your work so far!


On 11.12.2005, at 15:56, Joachim Henke wrote:

I just did some tests on the freedos image from your web-site and my first impression is that these crashes are something compiler related. When I
build qemu with

./configure --prefix=/usr/local --cc=gcc-3.3 --target-list=i386- softmmu --enable-cocoa

and start your image with

qemu -hda harddisk_1.img -soundhw sb16

it starts up and immediately crashes after 1 or 2 seconds (Bus error) - even before I could choose one of the 3 menu options. For the next test I
applied the patch below and compiled qemu with GCC 4.0.1:

--- Makefile.target
+++ Makefile.target
@@ -148,7 +148,7 @@

 ifeq ($(HAVE_GCC3_OPTIONS),yes)
 # very important to generate a return at the end of every operation
-OP_CFLAGS+=-fno-reorder-blocks -fno-optimize-sibling-calls
+OP_CFLAGS+=-fno-reorder-blocks -fno-optimize-sibling-calls -fno- tree-ch

 ifeq ($(CONFIG_DARWIN),yes)

./configure --prefix=/usr/local --cc=gcc-4.0 --target-list=i386- softmmu --enable-cocoa --disable-gcc-check

With this build everything seems to work perfectly. I boot into option 1 and run the DOOM demo with b.bat - it runs for ca. 100 seconds and then
quits back to DOS saying 'timed 2134 gametics in 2325 realtics'.

Can you try if using GCC 4 helps for you too? I'll do some more tests now.
Hopefully I can track down the problem to someting more specific.


Mike Kronenberg wrote:
You find a freedos including doom here:

or at the oszoo.org

- when choosing option 1 (standard)
about 10-20 sec into doom, when playing timedemo (doom -timedemo
demo3), otherwise, too.

This used to work great before.


Qemu-devel mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]