From: Brad Campbell <brad@wasp.net.au>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Which compiler to use to compile current SVN
Date: Mon, 28 Apr 2008 17:08:46 +0400 [thread overview]
Message-ID: <4815CC5E.6090108@wasp.net.au> (raw)
G'day all,
I can't get current SVN to compile at all here (same problem with regard to register spill other
people are seeing). I applied Blue Swirls patches (as seen here
http://lists.gnu.org/archive/html/qemu-devel/2008-03/msg00320.html) and cleaned up the rejects, but
I just get stumped further on...
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
/tracks/src/src/qemu.new/target-i386/helper.c
/tracks/src/src/qemu.new/target-i386/ops_sse.h: In function `helper_pshufw_mmx':
/tracks/src/src/qemu.new/target-i386/ops_sse.h:586: error: unable to find a register to spill in
class `GENERAL_REGS'
/tracks/src/src/qemu.new/target-i386/ops_sse.h:586: error: this is the insn:
(insn:HI 20 19 21 0 /tracks/src/src/qemu.new/target-i386/ops_sse.h:581 (set (strict_low_part
(subreg:HI (reg/v:DI 60 [ r ]) 0))
(mem/s/j:HI (plus:SI (mult:SI (reg:SI 64)
(const_int 2 [0x2]))
(reg/v/f:SI 62 [ s ])) [0 <variable>._w S2 A16])) 54 {*movstricthi_1} (insn_list 18
(insn_list 14 (insn_list 52 (nil))))
(expr_list:REG_DEAD (reg:SI 64)
(nil)))
/tracks/src/src/qemu.new/target-i386/ops_sse.h:586: confused by earlier errors, bailing out
make[1]: *** [helper.o] Error 1
make[1]: Leaving directory `/tracks/src/src/qemu.new/i386-softmmu'
make: *** [subdir-i386-softmmu] Error 2
brad@bklaptop2:~$ gcc --version
gcc (GCC) 4.2.3 (Ubuntu 4.2.3-2ubuntu7)
Copyright (C) 2007 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
brad@bklaptop2:~$ gcc-3.4 --version
gcc-3.4 (GCC) 3.4.6 (Ubuntu 3.4.6-6ubuntu3)
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
I'll download and compile a specific compiler if there is one guaranteed to compile cleanly (or even
work at all). What compilers are the major developers using that actually function?
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
next reply other threads:[~2008-04-28 13:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-28 13:08 Brad Campbell [this message]
2008-04-28 19:49 ` [Qemu-devel] Which compiler to use to compile current SVN Thiemo Seufer
2008-04-30 7:08 ` Brad Campbell
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=4815CC5E.6090108@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 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).