From: Peter Volkov <pva@gentoo.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] build failure on x86, any suggestions?
Date: Sat, 15 Mar 2008 17:01:49 +0300 [thread overview]
Message-ID: <1205589710.24804.65.camel@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 2407 bytes --]
Hello.
I just wanted to point developers attention to the following bug:
bugs.gentoo.org/212351 , comment #11 and further. The problem is that
qemu does not compile any more on x86. I've tried recent snapshot
(2008-03-15_05) and the problem persist there.
The problem gentoo is that previous versions are known to be affected to
security vulnerability so we'll have to mask it soon, while version
which does not build successfully will be masked too as there is no
reason to keep broken package in stable. Could anybody of developers
suggest anything on this issue? Thank you very much in advance!
The actual build error:
gcc -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/home/pva/work/qemu/qemu-snapshot-2008-03-15_05/target-i386
-I/home/pva/work/qemu/qemu-snapshot-2008-03-15_05 -MMD -MP -DNEED_CPU_H
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-I/home/pva/work/qemu/qemu-snapshot-2008-03-15_05/tcg
-I/home/pva/work/qemu/qemu-snapshot-2008-03-15_05/tcg/i386
-I/home/pva/work/qemu/qemu-snapshot-2008-03-15_05/fpu
-I/home/pva/work/qemu/qemu-snapshot-2008-03-15_05/linux-user
-I/home/pva/work/qemu/qemu-snapshot-2008-03-15_05/linux-user/i386 -c -o
op.o /home/pva/work/qemu/qemu-snapshot-2008-03-15_05/target-i386/op.c
/home/pva/work/qemu/qemu-snapshot-2008-03-15_05/target-i386/ops_sse.h:
In function `op_psrlq_mmx':
/home/pva/work/qemu/qemu-snapshot-2008-03-15_05/target-i386/ops_sse.h:213: error: unable to find a register to spill in class `GENERAL_REGS'
/home/pva/work/qemu/qemu-snapshot-2008-03-15_05/target-i386/ops_sse.h:213: error: this is the insn:
(insn:HI 36 35 37
3 /home/pva/work/qemu/qemu-snapshot-2008-03-15_05/target-i386/ops_sse.h:207 (parallel [
(set (reg:DI 63 [ <variable>.q ])
(lshiftrt:DI (reg:DI 63 [ <variable>.q ])
(subreg:QI (reg/v:SI 60 [ shift ]) 0)))
(clobber (scratch:SI))
(clobber (reg:CC 17 flags))
]) 309 {lshrdi3_1} (insn_list 33 (insn_list 35 (nil)))
(expr_list:REG_DEAD (reg/v:SI 60 [ shift ])
(expr_list:REG_UNUSED (reg:CC 17 flags)
(expr_list:REG_UNUSED (scratch:SI)
(nil)))))
--
Peter.
[-- Attachment #2: Эта часть сообщения подписана цифровой подписью --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2008-03-15 14:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-15 14:01 Peter Volkov [this message]
2008-03-15 14:20 ` [Qemu-devel] build failure on x86, any suggestions? Paul Brook
2008-03-15 15:13 ` Peter Volkov
2008-03-15 19:45 ` Alexander Graf
[not found] ` <200803151150.06813.computers57@hotmail.com>
[not found] ` <200803160001.52124.computers57@hotmail.com>
2008-03-16 6:01 ` C.W. Betts
2008-03-16 13:11 ` Peter Volkov
2008-03-16 16:20 ` Blue Swirl
[not found] ` <200803191436.55827.computers57@hotmail.com>
2008-03-19 20:36 ` C.W. Betts
2008-03-15 18:25 ` Stefan Weil
2008-03-15 20:35 ` Blue Swirl
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=1205589710.24804.65.camel@localhost \
--to=pva@gentoo.org \
--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).