qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] build failure on x86, any suggestions?
Date: Sat, 15 Mar 2008 22:35:45 +0200	[thread overview]
Message-ID: <f43fc5580803151335o5a85163exbf5c70e3ec49adf7@mail.gmail.com> (raw)
In-Reply-To: <1205589710.24804.65.camel@localhost>

[-- Attachment #1: Type: text/plain, Size: 1797 bytes --]

On 3/15/08, Peter Volkov <pva@gentoo.org> wrote:
> 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':

I can't replicate this bug, but does this patch (NB: not  a real fix)
make the compile successful or does it fail later somewhere else?

[-- Attachment #2: sse_test.diff --]
[-- Type: plain/text, Size: 460 bytes --]

      parent reply	other threads:[~2008-03-15 20:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-15 14:01 [Qemu-devel] build failure on x86, any suggestions? Peter Volkov
2008-03-15 14:20 ` 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 [this message]

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=f43fc5580803151335o5a85163exbf5c70e3ec49adf7@mail.gmail.com \
    --to=blauwirbel@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).