From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu 32-bit i386, gcc >= 3.4 spill error fix
Date: Mon, 5 May 2008 12:32:34 +0100 [thread overview]
Message-ID: <200805051232.35073.paul@codesourcery.com> (raw)
In-Reply-To: <cef699d70805041441i78ff3d06s989791f739ecf7ca@mail.gmail.com>
On Sunday 04 May 2008, Ben Taylor wrote:
> This patch applies some additional flags to op.c and helper.c
> for compiling on i386 32-bit systems with gcc >= 3.4.
>
> This has been tested on both ubuntu 7.10/32-bit and
> Solaris SXCE/32-bit with both gcc-3.3 and gcc-3.4
> and the behavior is consistent between both.
These hacks are sufficient fickle, and gcc versions sufficiently
meaningless[1], that I don't think we should do this. If you really want to
fix this, do it properly and finish the TCG conversion.
Paul
[1] As with most open source software a version number does not uniquely
identify a binary. In my experience pretty much noone uses unpatched FSF
releases directly.
prev parent reply other threads:[~2008-05-05 11:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-04 21:41 [Qemu-devel] Qemu 32-bit i386, gcc >= 3.4 spill error fix Ben Taylor
2008-05-05 1:13 ` [Qemu-devel] " Ben Taylor
2008-05-05 3:56 ` Aurelien Jarno
2008-05-05 5:17 ` Ben Taylor
2008-05-05 11:32 ` Paul Brook [this message]
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=200805051232.35073.paul@codesourcery.com \
--to=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 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.