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: Mon, 14 Nov 2011 17:18:49 +0200 [thread overview]
Message-ID: <4EC13159.6070209@redhat.com> (raw)
In-Reply-To: <CAFEAcA85jBwv7T4Ozj2T7MCiRhRTx8Wua_y8mkZFBRpsPStHSg@mail.gmail.com>
On 11/14/2011 05:15 PM, Peter Maydell wrote:
> >
> > We're unlikely to see testing before we apply the patch, and for oddball
> > archs, even afterwards.
>
> Yes, but if you put this change in just before release you
> get much less testing than if you do it with several months
> before release. This kind of change makes me nervous.
>
> > What we can do the qualify it on a build test
> > (and assume that if it builds, it runs, which I think is a safe assumption).
>
> 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.)
Is this assumption tested at runtime? If so, we can have the failure
message mumble something about building with --disable-pie.
> But yes, a build test would be a good start. (My money's
> on it failing to build on MacOSX.)
I'll post a v3 with an additional test.
> PS: what's the -DPIE needed for?
Copied from cookbook.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-11-14 15:18 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 [this message]
2011-11-14 18:45 ` Peter Maydell
2011-11-15 7:43 ` Avi Kivity
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=4EC13159.6070209@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 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).