Re: [PATCH] NEWS: Intel CET support hasn't be validated for i686

["H.J. Lu" <hjl dot tools at gmail dot com>]

On Thu, Jul 19, 2018 at 10:56 AM, Rical Jasan <rj@2c3t.io> wrote:
> On 07/19/2018 10:51 AM, H.J. Lu wrote:
> ...
>> diff --git a/NEWS b/NEWS
>> index daef815ae7..c6541f2004 100644
>> --- a/NEWS
>> +++ b/NEWS
>> @@ -17,7 +17,10 @@ Major new features:
>>    feature is currently supported on i386, x86_64 and x32 with GCC 8 and
>>    binutils 2.29 or later.  Note that CET-enabled glibc requires CPUs
>>    capable of multi-byte NOPs, like x86-64 processors as well as Intel
>> -  Pentium Pro or newer.
>> +  Pentium Pro or newer.  NOTE: --enable-cet has been tested for i686,
>> +  x86_64 and x32 on non-CET processors.  --enable-cet has been tested
>> +  for x86_64 and x32 on CET SDVs.  But Intel CET support hasn't been
>
> "SDVs, but"
>
>> +  validated for i686.
>>
>>  * The GNU C Library now has correct support for ABSOLUTE symbols
>>    (SHN_ABS-relative symbols).  Previously such ABSOLUTE symbols were
>> diff --git a/manual/install.texi b/manual/install.texi
>> index 3a87ac8bb5..61d3b1324a 100644
>> --- a/manual/install.texi
>> +++ b/manual/install.texi
>> @@ -148,6 +148,11 @@ Note that when CET is enabled, @theglibc{} requires CPUs capable of
>>  multi-byte NOPs, like x86-64 processors as well as Intel Pentium Pro or
>>  newer.
>>
>> +NOTE: @option{--enable-cet} has been tested for i686, x86_64 and x32
>> +on non-CET processors.  @option{--enable-cet} has been tested for
>> +x86_64 and x32 on CET SDVs.  But Intel CET support hasn't been validated
>
> Same here.
>

Like this?

-- 
H.J.

From 58dbe6cd8fb4f81ae0e858f832dfd6079f7e1bbb Mon Sep 17 00:00:00 2001
From: "H.J. Lu" <hjl.tools@gmail.com>
Date: Wed, 18 Jul 2018 14:55:46 -0700
Subject: [PATCH] INSTALL: Add a note for Intel CET status

	* NEWS: Add a note for Intel CET status.
	* manual/install.texi:  Add a note for Intel CET status.
	* INSTALL: Regenerated.
---
 INSTALL             | 5 +++++
 NEWS                | 5 ++++-
 manual/install.texi | 5 +++++
 3 files changed, 14 insertions(+), 1 deletion(-)

diff --git a/INSTALL b/INSTALL
index 844aa0f34c..840b862511 100644
--- a/INSTALL
+++ b/INSTALL
@@ -117,6 +117,11 @@ if 'CFLAGS' is specified it must enable optimization.  For example:
      the GNU C Library requires CPUs capable of multi-byte NOPs, like
      x86-64 processors as well as Intel Pentium Pro or newer.
 
+     NOTE: '--enable-cet' has been tested for i686, x86_64 and x32 on
+     non-CET processors.  '--enable-cet' has been tested for x86_64 and
+     x32 on CET SDVs, but Intel CET support hasn't been validated for
+     i686.
+
 '--disable-profile'
      Don't build libraries with profiling information.  You may want to
      use this option if you don't plan to do profiling.
diff --git a/NEWS b/NEWS
index daef815ae7..a8a64200e8 100644
--- a/NEWS
+++ b/NEWS
@@ -17,7 +17,10 @@ Major new features:
   feature is currently supported on i386, x86_64 and x32 with GCC 8 and
   binutils 2.29 or later.  Note that CET-enabled glibc requires CPUs
   capable of multi-byte NOPs, like x86-64 processors as well as Intel
-  Pentium Pro or newer.
+  Pentium Pro or newer.  NOTE: --enable-cet has been tested for i686,
+  x86_64 and x32 on non-CET processors.  --enable-cet has been tested
+  for x86_64 and x32 on CET SDVs, but Intel CET support hasn't been
+  validated for i686.
 
 * The GNU C Library now has correct support for ABSOLUTE symbols
   (SHN_ABS-relative symbols).  Previously such ABSOLUTE symbols were
diff --git a/manual/install.texi b/manual/install.texi
index 3a87ac8bb5..a8577dd610 100644
--- a/manual/install.texi
+++ b/manual/install.texi
@@ -148,6 +148,11 @@ Note that when CET is enabled, @theglibc{} requires CPUs capable of
 multi-byte NOPs, like x86-64 processors as well as Intel Pentium Pro or
 newer.
 
+NOTE: @option{--enable-cet} has been tested for i686, x86_64 and x32
+on non-CET processors.  @option{--enable-cet} has been tested for
+x86_64 and x32 on CET SDVs, but Intel CET support hasn't been validated
+for i686.
+
 @item --disable-profile
 Don't build libraries with profiling information.  You may want to use
 this option if you don't plan to do profiling.
-- 
2.17.1