From: Blue Swirl <blauwirbel@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Stefan Weil <sw@weilnetz.de>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] w32: Fix build with older gcc (unresolved symbol)
Date: Sat, 30 Mar 2013 13:44:14 +0000 [thread overview]
Message-ID: <CAAu8pHtf7VwxnBON8gy0qyhzpmemODtarhgDis1Cn-7YESS-GQ@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA_vEr1QKk8qHf8CkBiyeCmdh6vVFDaToWGPkTNHU47usQ@mail.gmail.com>
On Fri, Mar 29, 2013 at 5:58 PM, Peter Maydell <peter.maydell@linaro.org> wrote:
> On 29 March 2013 17:20, Stefan Weil <sw@weilnetz.de> wrote:
>> Maybe this modification is also needed for native gcc-4.4 and older
>> on Linux i386. If yes, we can move the new script code out of the
>> MinGW conditional code.
>
> There are at least a few people who want to run on older
> CPUs still (though the use of rdtsc doesn't help there, and
> we never did figure out how to identify whether we were
> compiling on a CPU which has rdtsc.)
Maybe for Linux (embedded i486 or whatsit). But host CPUs older than
i686 with Windows? We don't support Win2k as a host, would WinXP
support < i686?
>
> -- PMM
>
next prev parent reply other threads:[~2013-03-30 13:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 17:20 [Qemu-devel] [PATCH] w32: Fix build with older gcc (unresolved symbol) Stefan Weil
2013-03-29 17:58 ` Peter Maydell
2013-03-30 13:44 ` Blue Swirl [this message]
2013-03-30 13:50 ` Peter Maydell
2013-03-30 18:54 ` Blue Swirl
2013-05-10 20:14 ` Igor Mitsyanko
2013-05-11 6:41 ` Stefan Weil
2013-05-11 9:01 ` Igor Mitsyanko
2013-05-11 19:51 ` Stefan Weil
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=CAAu8pHtf7VwxnBON8gy0qyhzpmemODtarhgDis1Cn-7YESS-GQ@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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).