From: Avi Kivity <avi@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Blue Swirl <blauwirbel@gmail.com>, Paul Moore <pmoore@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1.0] configure: build position independent executables across the board, by default
Date: Tue, 15 Nov 2011 09:43:07 +0200 [thread overview]
Message-ID: <4EC2180B.6050204@redhat.com> (raw)
In-Reply-To: <CAFEAcA-hKK7JVsBm-mVe1jeR1-Juy1kLc9WWqRai__7a3eg4DA@mail.gmail.com>
On 11/14/2011 08:45 PM, Peter Maydell wrote:
> On 14 November 2011 15:18, Avi Kivity <avi@redhat.com> wrote:
> > On 11/14/2011 05:15 PM, Peter Maydell wrote:
> >> One of the failure cases I was thinking of is that if PIE means
> >> the platform's loader puts things in a different bit of the
> >> address space this might break TCG's assumptions about maximum
> >> distances between the codegen buffer and host C code. (That's
> >> a bug in TCG really but it would still be near-to-release
> >> breakage.)
>
> And indeed testing this on an ARM host running i386 TCG system
> mode, applying this patch causes qemu to fail at startup with
> a tcg abort due to an out of range jump.
>
> I've already said that ARM is going to be broken for 1.0 so
> that's not inherently a problem but it does indicate that
> we definitely need to test the other TCG target systems
> (and not just a "does it compile" test) if we want to put
> this change in.
I'll change the default to 'yes' for x86 hosts and 'no' for anything
else. tcg host maintainers can then update after testing/modifications.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2011-11-15 7:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 14:41 [Qemu-devel] [PATCH 1.0] configure: build position independent executables across the board, by default Avi Kivity
2011-11-14 14:59 ` Peter Maydell
2011-11-14 15:00 ` Peter Maydell
2011-11-14 15:06 ` Avi Kivity
2011-11-14 15:15 ` Peter Maydell
2011-11-14 15:18 ` Avi Kivity
2011-11-14 18:45 ` Peter Maydell
2011-11-15 7:43 ` Avi Kivity [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=4EC2180B.6050204@redhat.com \
--to=avi@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=pmoore@redhat.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 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.