From mboxrd@z Thu Jan 1 00:00:00 1970 From: Segher Boessenkool Subject: Re: [cryptodev:master 130/134] aes_generic.c:undefined reference to `_restgpr_31_x' Date: Fri, 12 Jan 2018 16:10:50 -0600 Message-ID: <20180112221050.GR21977@gate.crashing.org> References: <201801122249.RHvvGQJ6%fengguang.wu@intel.com> <20180112163946.GE21977@gate.crashing.org> <20180112204154.GM21977@gate.crashing.org> <20180112214111.GQ21977@gate.crashing.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "open list:HARDWARE RANDOM NUMBER GENERATOR CORE" , kbuild test robot , linuxppc-dev , Herbert Xu To: Arnd Bergmann Return-path: Received: from gate.crashing.org ([63.228.1.57]:41653 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965133AbeALWLL (ORCPT ); Fri, 12 Jan 2018 17:11:11 -0500 Content-Disposition: inline In-Reply-To: Sender: linux-crypto-owner@vger.kernel.org List-ID: On Fri, Jan 12, 2018 at 10:45:31PM +0100, Arnd Bergmann wrote: > > I guess you could enable the _x routines whenever you use ubsan? Ubsan > > will cause much bigger code growth than the handful of insns in those > > routines? > > Right, that could work, too. My patch that Herbert merged intentionally > used -Os also for non-UBSAN builds because it turned out to > be much faster (see gcc PR83651), "Much"? -Os is *slower* with 8.0, 5% faster with 7.2, 4% faster with 7.1, slower with 7.0 and 6.3. Your numbers, #c1. Anf this is the generic code of course, which is slow anyway (not to mention insecure). > but we could revert that back > to the default and only use the -Os for UBSAN, essentially > addressing only PR83356 but not PR83651. Segher