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>
Cc: "cmtice@google.com" <cmtice@google.com>
Subject: Re: [PATCH 15/22] Enable building libvtv with Intel CET
Date: Wed, 08 Nov 2017 17:33:00 -0000 [thread overview]
Message-ID: <e87a83d9-5569-0d39-7a3e-3a66c4c03d18@redhat.com> (raw)
In-Reply-To: <D511F25789BA7F4EBA64C8A63891A00291F4B955@IRSMSX102.ger.corp.intel.com>
On 10/31/2017 06:10 AM, Tsimbalist, Igor V wrote:
> The revised patch is attached. The differences are in what options are defined and propagated to Makefile for CET enabling.
> Â
> Ok for trunk?
>
> Igor
>
>
>> -----Original Message-----
>> From: Jeff Law [mailto:law@redhat.com]
>> Sent: Wednesday, October 18, 2017 1:38 AM
>> To: Tsimbalist, Igor V <igor.v.tsimbalist@intel.com>; gcc-
>> patches@gcc.gnu.org
>> Cc: cmtice@google.com
>> Subject: Re: [PATCH 15/22] Enable building libvtv with Intel CET
>>
>> On 10/12/2017 02:29 PM, Tsimbalist, Igor V wrote:
>>> Enable building libvtv with Intel CET options.
>>>
>>> libvtv/
>>> * acinclude.m4: Add enable.m4 and cet.m4.
>>> * libvtv/configure: Regenerate.
>>> * libvtv/configure.ac: Set CET_FLAGS. Update XCFLAGS.
>> Same comments as with libcilkrts.
>> Jeff
>>
>
> 0015-Enable-building-libvtv-with-Intel-CET.PATCH
>
>
> From cf1746f369de4fcd78bba197b05ba78f8b4f0b4e Mon Sep 17 00:00:00 2001
> From: Igor Tsimbalist <igor.v.tsimbalist@intel.com>
> Date: Tue, 15 Aug 2017 19:43:24 +0300
> Subject: [PATCH 15/21] Enable building libvtv with Intel CET
>
> libvtv/
> * acinclude.m4: Add enable.m4 and cet.m4.
> * Makefile.in: Regenerate.
> * testsuite/Makefile.in: Likewise.
> * configure: Likewise.
> * configure.ac: Set CET_FLAGS. Update XCFLAGS.
OK. Please wait to commit until entire set is ACK'd.
Jeff
prev parent reply other threads:[~2017-11-08 17:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 20:31 Tsimbalist, Igor V
2017-10-18 1:42 ` Jeff Law
2017-10-31 12:12 ` Tsimbalist, Igor V
2017-11-08 17:33 ` Jeff Law [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=e87a83d9-5569-0d39-7a3e-3a66c4c03d18@redhat.com \
--to=law@redhat.com \
--cc=cmtice@google.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).