Re: [tip:x86/seves] BUILD SUCCESS WITH WARNING e6eb15c9ba3165698488ae5c34920eea20eaa38e

Borislav Petkov
2020-09-15T18:49:50Z

On Tue, Sep 15, 2020 at 12:02:48PM -0500, Josh Poimboeuf wrote:
> If somebody can share the .o file, I can take a look.

If only I could reproduce...

So I built:

/home/share/src/llvm/tc-build/install/bin/clang-12 --version
ClangBuiltLinux clang version 12.0.0 (https://github.com/llvm/llvm-project 74a9c6d7e1c49cd0e3a8e8072b8aa03f7a84caff)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /home/share/src/llvm/tc-build/install/bin

and I don't trigger that warning even with that compiler.

What I do get is a lot of those pairs:

init/calibrate.o: warning: objtool: asan.module_ctor()+0xc: call without frame pointer save/setup
init/calibrate.o: warning: objtool: asan.module_dtor()+0xc: call without frame pointer save/setup
init/version.o: warning: objtool: asan.module_ctor()+0xc: call without frame pointer save/setup
init/version.o: warning: objtool: asan.module_dtor()+0xc: call without frame pointer save/setup
certs/system_keyring.o: warning: objtool: asan.module_ctor()+0xc: call without frame pointer save/setup
certs/system_keyring.o: warning: objtool: asan.module_dtor()+0xc: call without frame pointer save/setup
...

and a link fail at the end.

ld: arch/x86/events/core.o: in function `events_sysfs_show':
core.c:(.text+0x469b): undefined reference to `stpcpy'
ld: arch/x86/events/core.o: in function `events_ht_sysfs_show':
core.c:(.text+0x46f7): undefined reference to `stpcpy'
ld: drivers/tty/tty_io.o: in function `alloc_tty_struct':
tty_io.c:(.text+0x2da5): undefined reference to `stpcpy'
ld: drivers/tty/tty_io.o: in function `tty_register_device_attr':
tty_io.c:(.text+0x6a09): undefined reference to `stpcpy'
ld: drivers/tty/tty_io.o: in function `show_cons_active':
tty_io.c:(.text+0xa819): undefined reference to `stpcpy'
ld: drivers/scsi/scsi_transport_sas.o:scsi_transport_sas.c:(.text+0x6139): more undefined references to `stpcpy' follow
make: *** [Makefile:1166: vmlinux] Error 1

I'm thinking clang12 is too unstable to take it seriously...

--
Regards/Gruss,
Boris.