On Wed, Mar 20, 2019 at 10:55:06PM +0900, Masahiro Yamada wrote:
> On Sat, Mar 16, 2019 at 4:55 AM Matthias Kaehlcke wrote:
> >
> > Building the 32-bit vDSO with a recent clang version fails due
> > to undefined symbols:
> >
> > arch/x86/entry/vdso/vdso32.so.dbg: undefined symbols found
> >
> >
On Sat, Mar 16, 2019 at 6:32 AM Nick Desaulniers
wrote:
>
> On Fri, Mar 15, 2019 at 12:54 PM Matthias Kaehlcke wrote:
> >
> > Building the 32-bit vDSO with a recent clang version fails due
> > to undefined symbols:
> >
> > arch/x86/entry/vdso/vdso32.so.dbg: undefined symbols found
> >
> > The
On Sat, Mar 16, 2019 at 4:55 AM Matthias Kaehlcke wrote:
>
> Building the 32-bit vDSO with a recent clang version fails due
> to undefined symbols:
>
> arch/x86/entry/vdso/vdso32.so.dbg: undefined symbols found
>
> The undefined symbol in this case is __lshrdi3, which is part of
> the compiler
On Mon, Mar 18, 2019 at 01:44:35PM -0700, Matthias Kaehlcke wrote:
> You have a point, enabling -Oz (aggressive optimization for size)
> doesn't seem a good choice for the entire kernel.
Note that in this instance, -Os actually generates _smaller_ code than
-Oz, now that's mostly because of
Hi Peter,
On Mon, Mar 18, 2019 at 06:16:04PM +0100, Peter Zijlstra wrote:
> On Mon, Mar 18, 2019 at 10:09:37AM -0700, Nick Desaulniers wrote:
> > On Fri, Mar 15, 2019 at 3:29 PM Matthias Kaehlcke wrote:
> > > On Fri, Mar 15, 2019 at 02:31:09PM -0700, 'Nick Desaulniers' via Clang
> > > Built
On Mon, Mar 18, 2019 at 10:09:37AM -0700, Nick Desaulniers wrote:
> On Fri, Mar 15, 2019 at 3:29 PM Matthias Kaehlcke 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
> >
On Fri, Mar 15, 2019 at 3:29 PM Matthias Kaehlcke 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
On Fri, Mar 15, 2019 at 04:18:31PM -0700, h...@zytor.com wrote:
> Note: it is also probably no reason to use -Os/-Oz for the vdso.
Is anyone actually using -Os and CONFIG_CC_OPTIMIZE_FOR_SIZE ? I've been
staring at compiler output a lot lately and -Os really generates
atrocious crap.
That is,
On March 15, 2019 3:29:06 PM PDT, Matthias Kaehlcke wrote:
>Hi Nick,
>
>On Fri, Mar 15, 2019 at 02:31:09PM -0700, 'Nick Desaulniers' via Clang
>Built Linux wrote:
>> On Fri, Mar 15, 2019 at 12:54 PM Matthias Kaehlcke
>wrote:
>> >
>> > Building the 32-bit vDSO with a recent clang version fails
Hi Nick,
On Fri, Mar 15, 2019 at 02:31:09PM -0700, 'Nick Desaulniers' via Clang Built
Linux wrote:
> On Fri, Mar 15, 2019 at 12:54 PM Matthias Kaehlcke wrote:
> >
> > Building the 32-bit vDSO with a recent clang version fails due
> > to undefined symbols:
> >
> >
On Fri, Mar 15, 2019 at 12:54 PM Matthias Kaehlcke wrote:
>
> Building the 32-bit vDSO with a recent clang version fails due
> to undefined symbols:
>
> arch/x86/entry/vdso/vdso32.so.dbg: undefined symbols found
>
> The undefined symbol in this case is __lshrdi3, which is part of
> the compiler
Building the 32-bit vDSO with a recent clang version fails due
to undefined symbols:
arch/x86/entry/vdso/vdso32.so.dbg: undefined symbols found
The undefined symbol in this case is __lshrdi3, which is part of
the compiler runtime library, however the vDSO isn't linked against
this library.
12 matches
Mail list logo