From: Kevin Wolf <kwolf@redhat.com>
To: Bug 902148 <902148@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [Bug 902148] Re: qemu-img V1.0 hangs on creating Image (0.15.1 runs)
Date: Mon, 09 Jan 2012 12:25:52 +0100 [thread overview]
Message-ID: <4F0ACEC0.6010405@redhat.com> (raw)
In-Reply-To: <CAJSP0QVs4_kAAmQDGSDqbKpAcXZBJfqPvoV8iHiDEnsvfrRa8g@mail.gmail.com>
Am 20.12.2011 17:49, schrieb Stefan Hajnoczi:
> On Tue, Dec 20, 2011 at 3:25 PM, Michael Niehren
> <902148@bugs.launchpad.net> wrote:
>> here we are. Attached the tgz. I am using no spezial distribution, it's a self compiled LFS with
>> gcc V4.5.1
>>
>> Is there a different compiler-call if i use --enable-debug, which then
>> works ?
>
> Richard Sandiford looked at your gcc -fdump-tree-all-details output
> and suggests that this bug has been fixed in gcc 4.5.3:
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45967
>
> Using the most recent gcc should fix the issue you are seeing.
Can we add some workaround? Not sure what will work, maybe a simple
compiler barrier?
Kevin
next prev parent reply other threads:[~2012-01-09 11:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 13:10 [Qemu-devel] [Bug 902148] [NEW] qemu-img V1.0 hangs on creating Image (0.15.1 runs) Michael Niehren
2011-12-12 10:09 ` Stefan Hajnoczi
2011-12-19 10:02 ` [Qemu-devel] [Bug 902148] " Michael Niehren
2011-12-19 10:31 ` Stefan Hajnoczi
2011-12-19 10:52 ` Michael Niehren
2011-12-19 13:22 ` Stefan Hajnoczi
2011-12-19 17:26 ` Michael Niehren
2011-12-20 8:04 ` Stefan Hajnoczi
2011-12-20 10:17 ` Michael Niehren
2011-12-20 10:25 ` Michael Niehren
2011-12-20 10:49 ` Stefan Hajnoczi
2011-12-20 11:53 ` Stefan Hajnoczi
2011-12-20 15:25 ` Michael Niehren
2011-12-20 16:49 ` Stefan Hajnoczi
2011-12-20 21:45 ` Stefan Hajnoczi
2012-01-09 11:25 ` Kevin Wolf [this message]
2012-01-09 13:00 ` Stefan Hajnoczi
2012-01-14 15:40 ` Zhi Yong Wu
2012-01-15 11:14 ` Stefan Hajnoczi
2012-01-16 2:44 ` Zhi Yong Wu
2011-12-20 16:51 ` Stefan Hajnoczi
2011-12-20 23:59 ` Michael Niehren
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=4F0ACEC0.6010405@redhat.com \
--to=kwolf@redhat.com \
--cc=902148@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.com \
/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.