From: Richard Henderson <rth@twiddle.net>
To: Bug 1218098 <1218098@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1218098] Re: qemu-system-ppc64 segfaults in helper_ldl_mmu
Date: Thu, 29 Aug 2013 08:28:38 -0700 [thread overview]
Message-ID: <521F68A6.2010800@twiddle.net> (raw)
In-Reply-To: <20130829112551.20693.65241.malone@chaenomeles.canonical.com>
On 08/29/2013 04:25 AM, agraf wrote:
> I just bisected the same thing down to this commit. It only breaks on
> one of my x86 machines though. Namely one with
>
> gcc (SUSE Linux) 4.7.2 20130108 [gcc-4_7-branch revision 195012]
Yes, it requires a compiler and compile options resulting in the right
sequence of tail calls. Patch and analysis here:
http://patchwork.ozlabs.org/patch/270872/
r~
next prev parent reply other threads:[~2013-08-29 15:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 22:33 [Qemu-devel] [Bug 1218098] [NEW] qemu-system-ppc64 segfaults in helper_ldl_mmu Richard Jones
2013-08-28 22:38 ` [Qemu-devel] [Bug 1218098] " Richard Jones
2013-08-28 22:52 ` Richard Jones
2013-08-29 11:25 ` agraf
2013-08-29 15:28 ` Richard Henderson [this message]
2013-08-29 16:27 ` Richard Henderson
2013-08-29 20:22 ` Richard Henderson
2016-06-22 13:30 ` T. Huth
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=521F68A6.2010800@twiddle.net \
--to=rth@twiddle.net \
--cc=1218098@bugs.launchpad.net \
--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).