[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190318171604.GU6058@hirez.programming.kicks-ass.net>
Date: Mon, 18 Mar 2019 18:16:04 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Nick Desaulniers <ndesaulniers@...gle.com>
Cc: Matthias Kaehlcke <mka@...omium.org>,
Andy Lutomirski <luto@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
"H . Peter Anvin" <hpa@...or.com>, x86@...nel.org,
LKML <linux-kernel@...r.kernel.org>,
Manoj Gupta <manojgupta@...omium.org>,
Tiancong Wang <tcwang@...omium.org>,
Stephen Hines <srhines@...gle.com>,
clang-built-linux@...glegroups.com,
Masahiro Yamada <yamada.masahiro@...ionext.com>
Subject: Re: [PATCH] x86/vdso: include generic __lshrdi3 in 32-bit vDSO
On Mon, Mar 18, 2019 at 10:09:37AM -0700, Nick Desaulniers wrote:
> On Fri, Mar 15, 2019 at 3:29 PM Matthias Kaehlcke <mka@...omium.org> wrote:
> > On Fri, Mar 15, 2019 at 02:31:09PM -0700, 'Nick Desaulniers' via Clang Built Linux wrote:
> > > Is there a config I can set to reproduce this, in order to help
> > > test?
> >
> > I encountered it with a Chrome OS specific configuration, but a
> > defconfig should do.
>
> defconfig selects CONFIG_OPTIMIZE_FOR_PERFORMANCE=y. I needed to
> select CONFIG_CC_OPTIMIZE_FOR_SIZE=y to repro. My CI is simply
> running defconfigs, which is why I didn't catch this.
I suspect the right fix is to make clang use -Os and abolish that -Oz
madness.
Powered by blists - more mailing lists