From: "H.J. Lu" <hjl.tools@gmail.com>
To: Richard Earnshaw <rearnsha@arm.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: PATCH: Add check_lto_available
Date: Fri, 11 Oct 2013 17:09:00 -0000 [thread overview]
Message-ID: <CAMe9rOrF8pQ5_1cZJa057QQGG5HDsdPT1Ss7tgu3-Y-drMJUbQ@mail.gmail.com> (raw)
In-Reply-To: <5257F0CE.1030804@arm.com>
On Fri, Oct 11, 2013 at 5:36 AM, Richard Earnshaw <rearnsha@arm.com> wrote:
> HJ,
>
> Why does this patch try to produce a shared object as part of
> determining whether LTO works? If you have LTO but not shared object
> support in a toolchain this means we don't test LTO properly.
>
LTO tests also check if shared library works correctly with LTO.
--
H.J.
next prev parent reply other threads:[~2013-10-11 17:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 17:58 H.J. Lu
2013-10-11 12:36 ` Richard Earnshaw
2013-10-11 17:09 ` H.J. Lu [this message]
2013-10-14 10:16 ` Vidya Praveen
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=CAMe9rOrF8pQ5_1cZJa057QQGG5HDsdPT1Ss7tgu3-Y-drMJUbQ@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=binutils@sourceware.org \
--cc=rearnsha@arm.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 read-only IMAP folder(s) and NNTP newsgroup(s).