qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Ben Taylor" <bentaylor.solx86@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Which compiler to use to compile current SVN
Date: Wed, 30 Apr 2008 07:15:03 -0400	[thread overview]
Message-ID: <cef699d70804300415v73bea9c4o175c1173b4ae4e63@mail.gmail.com> (raw)
In-Reply-To: <20080430093229.GA14419@networkno.de>

On Wed, Apr 30, 2008 at 5:32 AM, Thiemo Seufer <ths@networkno.de> wrote:
> Brad Campbell wrote:
>  > Thiemo Seufer wrote:
>  >
>  >>> gcc-3.4  -fomit-frame-pointer -I. -I..
>  >>> -I/tracks/src/src/qemu.new/target-i386 -I/tracks/src/src/qemu.new
>  >>> -MMD -MP -DNEED_CPU_H -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64
>  >>> -D_LARGEFILE_SOURCE -I/tracks/src/src/qemu.new/tcg
>  >>> -I/tracks/src/src/qemu.new/tcg/i386 -I/tracks/src/src/qemu.new/fpu
>  >>> -DHAS_AUDIO -DHAS_AUDIO_CHOICE -I/tracks/src/src/qemu.new/slirp
>  >>> -march=pentium-mmx -Wall -O2 -g -fno-strict-aliasing  -m32 -c -o
>  >>> helper.o
>  >>   ^^^^^^^^^^^^^^^^^^
>  >>
>  >> Too much optimization. IIRC a known problem, -march needs to be a pre-MMX
>  >> cpu.
>  >
>  > So I'd believed.. however, I've tried -march=[i386,i486,i586,i686,pentium,pentium-mmx] ...
>
>  Ok, then I don't know why it fails in your environment.
>
>  [snip]
>
> > How is _anybody_ compiling this source?
>  > Someone please give me a clue here...
>
>  I use plain Debian stable.

Just to note, I'm seeing this on Solaris x86 with gcc-3.4.3 on 32-bit
systems as well.

I'm in the process of building gcc-3.4.6 but that will be a few more days before
it's ready.

Ben

  reply	other threads:[~2008-04-30 11:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-28 13:08 [Qemu-devel] Which compiler to use to compile current SVN Brad Campbell
2008-04-28 19:49 ` Thiemo Seufer
2008-04-30  7:08   ` Brad Campbell
2008-04-30  9:32     ` Thiemo Seufer
2008-04-30 11:15       ` Ben Taylor [this message]
2008-04-30 12:34         ` WaxDragon
2008-04-30 18:47       ` Brad Campbell

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=cef699d70804300415v73bea9c4o175c1173b4ae4e63@mail.gmail.com \
    --to=bentaylor.solx86@gmail.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).