From: "Steve D. Perkins" <lists@steveperkins.net>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Patch Submission] QEMU with GCC/Win32
Date: Sat, 30 Jul 2005 19:16:09 -0400 [thread overview]
Message-ID: <42EC0A39.40404@steveperkins.net> (raw)
In-Reply-To: <200507310004.28470.paul@codesourcery.com>
Paul Brook wrote:
>"sledgehammer" and "nut" spring to mind :-)
>
>The attached patch is sufficient to get qemu working on win32 when compiled with gcc3.4. I've successfully booted a knoppix CD inside qemu on a windows host with this patch.
>
>The problem was that gcc is choosing inconvenient names for static local variables. These symbols are never supposed to be seen outside the compiler, so it's allowed to change these at random. The solution is to use explicitly specify the asm name for the variable.
>
>Paul
>
>
Haha... thanks alot Paul! I now have a big bruise from slapping my
palm against my forehead... seeing how much more simplified the changes
could be after I went through all that hassle editing "dyngen.c"!
Given that QEMU can support the current release of GCC on Windows by
changing less than 40 lines of code in one file, can we please begin
discussing the inclusion of these changes in the main codebase?
Explicitly specifying this one variable name in a preprocessor directive
doesn't look as if it would affect builds on other platforms, but it
would be easy enough to test either way.
Steve
next prev parent reply other threads:[~2005-07-30 23:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-30 18:42 [Qemu-devel] [Patch Submission] QEMU with GCC/Win32 Steve D. Perkins
2005-07-30 19:13 ` Paul Brook
2005-07-30 19:41 ` Steve D. Perkins
2005-07-30 21:16 ` Filip Navara
2005-07-30 21:28 ` Christian MICHON
2005-07-30 23:04 ` Steve D. Perkins
2005-07-30 23:04 ` Paul Brook
2005-07-30 23:16 ` Steve D. Perkins [this message]
2005-07-30 23:39 ` Paul Brook
2005-08-01 11:34 ` Gwenole Beauchesne
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=42EC0A39.40404@steveperkins.net \
--to=lists@steveperkins.net \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).