From: Jeff Law <law@redhat.com>
To: "Tsimbalist, Igor V" <igor.v.tsimbalist@intel.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 11/22] Enable building libatomic with Intel CET
Date: Wed, 18 Oct 2017 01:42:00 -0000 [thread overview]
Message-ID: <759db626-b27a-1971-f299-5876de5ae81d@redhat.com> (raw)
In-Reply-To: <D511F25789BA7F4EBA64C8A63891A00291F422D6@IRSMSX102.ger.corp.intel.com>
On 10/12/2017 02:18 PM, Tsimbalist, Igor V wrote:
> Enable building libatomic with CET options.
>
> libatomic/
> * configure.ac: Set CET_FLAGS, update XCFLAGS.
> * acinclude.m4: Add cet.m4 and enable.m4.
> * configure: Regenerate.
> * Makefile.in: Likewise.
> * testsuite/Makefile.in: Likewise.
>
Same comments as with libcilkrts.
Jeff
next prev parent reply other threads:[~2017-10-18 1:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 20:20 Tsimbalist, Igor V
2017-10-18 1:42 ` Jeff Law [this message]
2017-10-31 12:00 ` Tsimbalist, Igor V
2017-11-08 17:31 ` Jeff Law
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=759db626-b27a-1971-f299-5876de5ae81d@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=igor.v.tsimbalist@intel.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).