qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Aaron Elkins <threcius@yahoo.com>,
	"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Qemu: Guest Linux hangs on Mac OS X 10.11
Date: Mon, 9 Nov 2015 11:46:49 +0000	[thread overview]
Message-ID: <CAFEAcA8ihZKQKSa3VbL7vOV+6p53d=L108Rvq5A-OUe9QkS0bQ@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA9oery-wy5rjFqEaQ1DWrYWR9zMRzWb3HPWAcbmMCDi3w@mail.gmail.com>

On 9 November 2015 at 11:06, Peter Maydell <peter.maydell@linaro.org> wrote:
> On 9 November 2015 at 10:21, Paolo Bonzini <pbonzini@redhat.com> wrote:
>> Hmm, so the list is pretty short:
>
> The good news is that my second bisect conclusively fingered
> the culprit for why the bug went away...
>
>>       configure: disable FORTIFY_SOURCE under clang
>
> ...the bad news is it's because this patch inadvertently makes
> all non-fortify-source compiles be no-optimization (and we already
> knew the bug didn't repro in an unoptimized build).

Yep, just confirmed that current master with commit b553a0428
reverted displays the bug again.

thanks
-- PMM

  reply	other threads:[~2015-11-09 11:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-16  7:32 [Qemu-devel] Qemu: Guest Linux hangs on Mac OS X 10.11 Aaron Elkins
2015-10-18 19:46 ` Peter Maydell
2015-10-18 20:37   ` Peter Maydell
2015-10-19  5:09     ` Aaron Elkins
2015-10-19  5:50     ` Aaron Elkins
2015-11-08 22:55     ` Peter Maydell
2015-11-09  9:10       ` Paolo Bonzini
2015-11-09 10:02         ` Peter Maydell
2015-11-09 10:21           ` Paolo Bonzini
2015-11-09 11:06             ` Peter Maydell
2015-11-09 11:46               ` Peter Maydell [this message]
2015-11-09 13:30                 ` Peter Maydell
2015-11-09 13:40                   ` Paolo Bonzini
2015-11-09 14:26                     ` Peter Maydell
2015-11-09 16:59 ` Peter Maydell

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='CAFEAcA8ihZKQKSa3VbL7vOV+6p53d=L108Rvq5A-OUe9QkS0bQ@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=threcius@yahoo.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 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).