From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <segher@kernel.crashing.org>
Received: from gate.crashing.org (gate.crashing.org [63.228.1.57])
 by sourceware.org (Postfix) with ESMTP id 129113896C10
 for <gcc-patches@gcc.gnu.org>; Wed, 12 May 2021 23:26:12 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 129113896C10
Authentication-Results: sourceware.org; dmarc=none (p=none dis=none)
 header.from=kernel.crashing.org
Authentication-Results: sourceware.org;
 spf=fail smtp.mailfrom=segher@kernel.crashing.org
Received: from gate.crashing.org (localhost.localdomain [127.0.0.1])
 by gate.crashing.org (8.14.1/8.14.1) with ESMTP id 14CNPCd4032322;
 Wed, 12 May 2021 18:25:12 -0500
Received: (from segher@localhost)
 by gate.crashing.org (8.14.1/8.14.1/Submit) id 14CNPBPk032320;
 Wed, 12 May 2021 18:25:11 -0500
X-Authentication-Warning: gate.crashing.org: segher set sender to
 segher@kernel.crashing.org using -f
Date: Wed, 12 May 2021 18:25:11 -0500
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Bill Schmidt <wschmidt@linux.ibm.com>
Cc: will schmidt <will_schmidt@vnet.ibm.com>, gcc-patches@gcc.gnu.org,
 dje.gcc@gmail.com
Subject: Re: [PATCH 4/4] rs6000: Add ROP tests
Message-ID: <20210512232511.GD10366@gate.crashing.org>
References: <cover.1619400506.git.wschmidt@linux.ibm.com>
 <4adcb20b3d2d578fe6f34a9b5cd400f9999b54f5.1619400506.git.wschmidt@linux.ibm.com>
 <7118acced8c2c6a60d86cceff306ac55dfcdb115.camel@vnet.ibm.com>
 <32475e36-6494-10ec-3ebb-4c43d7f9cea8@linux.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <32475e36-6494-10ec-3ebb-4c43d7f9cea8@linux.ibm.com>
User-Agent: Mutt/1.4.2.3i
X-Spam-Status: No, score=-6.5 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL,
 KAM_DMARC_STATUS, TXREP, T_SPF_HELO_PERMERROR,
 T_SPF_PERMERROR autolearn=no autolearn_force=no version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
 server2.sourceware.org
X-BeenThere: gcc-patches@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-patches mailing list <gcc-patches.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-patches>,
 <mailto:gcc-patches-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-patches/>
List-Post: <mailto:gcc-patches@gcc.gnu.org>
List-Help: <mailto:gcc-patches-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-patches>,
 <mailto:gcc-patches-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 12 May 2021 23:26:14 -0000

On Mon, Apr 26, 2021 at 02:27:45PM -0500, Bill Schmidt wrote:
> On 4/26/21 11:04 AM, will schmidt wrote:
> >Does there need to be another test to verify if -mrop-protect is on by
> >default without specifying -mrop-protect?   (or is it?)  Question on
> >0/4.
> 
> It's off by default (see the Init(0) in patch 1/4).

And in general we only need a test for it if the default isn't fixed.


Segher