public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>,
	Alexandre Oliva <aoliva@redhat.com>,
		Paolo Bonzini <paolo.bonzini@gmail.com>,
	DJ Delorie <dj@redhat.com>
Subject: PING^2: [PATCH Filter out -fsanitize=address if not in combined tree in lto-plugin
Date: Fri, 11 Jan 2013 14:01:00 -0000	[thread overview]
Message-ID: <CAMe9rOqno2YS8E2S7E72MffZUN9Bf+bta6kd0Z_nYHB1n32jhA@mail.gmail.com> (raw)

On Wed, Dec 12, 2012 at 6:21 AM, H.J. Lu <hjl.tools@gmail.com> wrote:
> On Thu, Nov 29, 2012 at 9:38 AM, H.J. Lu <hongjiu.lu@intel.com> wrote:
>> Hi,
>>
>> When GCC is configured with --with-build-config="bootstrap-asan", all
>> -flto tests will fail since -fsanitize=address is used to compile
>> liblto_plugin.so and linker isn't compiled with -fsanitize=address.
>> This patch filters out -fsanitize=address from CFLAGS if we aren't
>> in a combined tree with binutils.  OK to install?
>>
>>
>> H.J.
>> ---
>> ---
>>  lto-plugin/Makefile.am    |  7 +++++++
>>  lto-plugin/Makefile.in    |  5 +++++
>>  lto-plugin/configure      | 18 +++++++++++++++---
>>  lto-plugin/configure.ac   |  4 ++++
>>  5 files changed, 39 insertions(+), 3 deletions(-)
>>  create mode 100644 lto-plugin/ChangeLog.asan
>>
>> 2012-11-21  H.J. Lu  <hongjiu.lu@intel.com>
>>
>>         * Makefile.am (CFLAGS): Filter out -fsanitize=address if not
>>         in a combined tree of GCC and binutils.
>>         (LDFLAGS): Likewise.
>>         * configure.ac (COMBINED_TREE): New AM_CONDITIONAL.
>>         * Makefile.in: Regenerated.
>>         * configure: Likewise.
>>
>
> PING.
>

PING.

-- 
H.J.

                 reply	other threads:[~2013-01-11 14:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAMe9rOqno2YS8E2S7E72MffZUN9Bf+bta6kd0Z_nYHB1n32jhA@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=aoliva@redhat.com \
    --cc=dj@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=paolo.bonzini@gmail.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).