qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: "Blue Swirl" <blauwirbel@gmail.com>,
	"Alexander Graf" <agraf@suse.de>,
	"Andreas Färber" <afaerber@suse.de>
Subject: [Qemu-devel] qemu-1.0-rc1 delayed (need fix for PPC32 build)
Date: Tue, 08 May 2012 20:52:17 -0500	[thread overview]
Message-ID: <4FA9CDD1.4050105@us.ibm.com> (raw)

Hi,

I was hoping we'd have a solution by now but it looks like we don't.  I'm going 
to delay the qemu-1.0-rc1 release until tomorrow.  I'd like to propose a couple 
paths forward.  Here's my understanding of the situation:

1) TCG changes were made for the Sparc/Alpha targets that use AREG0

2) AREG0 never worked properly on ppc32 hosts

3) Until recently, this caused a runtime failure of the Sparc/Alpha targets on 
ppc32.  However, malc recently changed this to a build time failure.

I don't feel comfortable shipping a release candidate with a known failing 
build.  Here are the options:

a) Revert malc's change.  I don't think this is much better than shipping a 
broken build.

b) Disable sparc/alpha targets in default_target_list on ppc32 hosts.  I think 
is probably the best short term approach.

c) Wait for Andreas' patches (I believe Alex detected a problem in the current 
version).

Unless anyone strongly objects, I'm going to implement (b) tomorrow morning so 
we can keep the -rc cycle moving.  I would hope that we'll have something worked 
out for (c) by -rc2.

Regards,

Anthony Liguori

             reply	other threads:[~2012-05-09  1:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-09  1:52 Anthony Liguori [this message]
2012-05-09  1:56 ` [Qemu-devel] qemu-1.0-rc1 delayed (need fix for PPC32 build) malc
2012-05-09 14:21 ` Artyom Tarasenko

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=4FA9CDD1.4050105@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=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).