All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Campbell <brad@wasp.net.au>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Which compiler to use to compile current SVN
Date: Wed, 30 Apr 2008 11:08:09 +0400	[thread overview]
Message-ID: <48181AD9.1070604@wasp.net.au> (raw)
In-Reply-To: <20080428194912.GE16597@networkno.de>

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] ...

gcc-3.4 -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=i386 -Wall -O2 -g -fno-strict-aliasing  -m32 -c -o kqemu.o 
/tracks/src/src/qemu.new/kqemu.c
gcc-3.4 -march=i386 -Wall -O2 -g -fno-strict-aliasing  -fno-reorder-blocks  -fno-gcse 
-fno-optimize-sibling-calls  -fno-crossjumping  -fno-align-labels  -fno-align-jumps 
-fno-align-functions   -mpreferred-stack-boundary=2 -fomit-frame-pointer  -m32 -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 -c -o op.o /tracks/src/src/qemu.new/target-i386/op.c
/tracks/src/src/qemu.new/target-i386/ops_sse.h: In function `op_pshufw_mmx':
/tracks/src/src/qemu.new/target-i386/ops_sse.h:597: error: unable to find a register to spill in 
class `GENERAL_REGS'
/tracks/src/src/qemu.new/target-i386/ops_sse.h:597: error: this is the insn:
(insn:HI 18 17 19 0 /tracks/src/src/qemu.new/target-i386/ops_sse.h:592 (set (strict_low_part 
(subreg:HI (reg/v:DI 58 [ r ]) 0))
         (mem/s/j:HI (plus:SI (mult:SI (reg:SI 62)
                     (const_int 2 [0x2]))
                 (reg/v/f:SI 60 [ s ])) [0 <variable>._w S2 A16])) 54 {*movstricthi_1} (insn_list 16 
(insn_list 12 (insn_list 50 (nil))))
     (expr_list:REG_DEAD (reg:SI 62)
         (nil)))
/tracks/src/src/qemu.new/target-i386/ops_sse.h:597: confused by earlier errors, bailing out
make[1]: *** [op.o] Error 1
make[1]: Leaving directory `/tracks/src/src/qemu.new/i386-softmmu'
make: *** [subdir-i386-softmmu] Error 2

brad@bklaptop2:/tracks/src/src/qemu.new$ cat build
#!/bin/bash

make clean
CFLAGS=-march=i386 ./configure --target-list=i386-softmmu --enable-alsa
make

brad@bklaptop2:/tracks/src/src/qemu.new$ cat Makefile.target | grep march
OP_CFLAGS := -march=i386 -Wall -O2 -g -fno-strict-aliasing

How is _anybody_ compiling this source?
Someone please give me a clue here...

Brad
-- 
"Human beings, who are almost unique in having the ability
to learn from the experience of others, are also remarkable
for their apparent disinclination to do so." -- Douglas Adams

  reply	other threads:[~2008-04-30  7:58 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 [this message]
2008-04-30  9:32     ` Thiemo Seufer
2008-04-30 11:15       ` Ben Taylor
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=48181AD9.1070604@wasp.net.au \
    --to=brad@wasp.net.au \
    --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.