From: Brad <brad@comstyle.com>
To: Avi Kivity <avi@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 1.0] configure: tighten pie toolchain support test for tls variables
Date: Tue, 22 Nov 2011 21:54:44 -0500 [thread overview]
Message-ID: <4ECC6074.9070906@comstyle.com> (raw)
In-Reply-To: <1321965325-32050-1-git-send-email-avi@redhat.com>
On 22/11/11 7:35 AM, Avi Kivity wrote:
> Some toolchains don't support pie properly when tls variables are
> in use. Disallow pie when such toolchains are detected.
>
> Signed-off-by: Avi Kivity<avi@redhat.com>
> ---
>
> v2: give tls_var a type; avoids invisible warning
This breaks the PIE check on OpenBSD since there is no TLS
support and the issue trying to be detected doesn't affect
OpenBSD.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
prev parent reply other threads:[~2011-11-23 2:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 12:35 [Qemu-devel] [PATCH v2 1.0] configure: tighten pie toolchain support test for tls variables Avi Kivity
2011-11-23 2:54 ` Brad [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=4ECC6074.9070906@comstyle.com \
--to=brad@comstyle.com \
--cc=avi@redhat.com \
--cc=kraxel@redhat.com \
--cc=pbonzini@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).