From: Borislav Petkov <bp@alien8.de>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
Rong Chen <rong.a.chen@intel.com>,
kernel test robot <lkp@intel.com>,
"Li, Philip" <philip.li@intel.com>, x86-ml <x86@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [tip:x86/seves] BUILD SUCCESS WITH WARNING e6eb15c9ba3165698488ae5c34920eea20eaa38e
Date: Tue, 15 Sep 2020 19:21:52 +0200 [thread overview]
Message-ID: <20200915172152.GR14436@zn.tnic> (raw)
In-Reply-To: <20200915170248.gcv54pvyckteyhk3@treble>
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.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2020-09-15 18:49 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 13:42 [tip:x86/seves] BUILD SUCCESS WITH WARNING e6eb15c9ba3165698488ae5c34920eea20eaa38e kernel test robot
2020-09-15 13:55 ` Borislav Petkov
2020-09-15 14:18 ` Rong Chen
2020-09-15 14:41 ` Borislav Petkov
2020-09-15 16:05 ` Borislav Petkov
2020-09-15 17:02 ` Josh Poimboeuf
2020-09-15 17:21 ` Borislav Petkov [this message]
2020-09-15 17:34 ` Borislav Petkov
2020-09-15 17:41 ` Nick Desaulniers
2020-09-15 18:01 ` Borislav Petkov
2020-09-15 18:04 ` Nick Desaulniers
2020-09-15 17:40 ` Nick Desaulniers
2020-09-15 18:09 ` Marco Elver
2020-09-16 8:30 ` peterz
2020-09-16 8:46 ` Marco Elver
2020-09-16 9:06 ` peterz
2020-09-16 9:33 ` Marco Elver
2020-09-16 18:22 ` Nick Desaulniers
2020-09-16 18:51 ` Marco Elver
2020-09-17 4:11 ` Fangrui Song
[not found] ` <333D40A0-4550-4309-9693-1ABA4AC75399@arm.com>
2020-09-17 11:04 ` Mark Rutland
2020-09-17 11:16 ` Daniel Kiss
2020-09-17 18:39 ` Josh Poimboeuf
2020-09-15 17:44 ` Nick Desaulniers
2020-09-15 20:12 ` Nick Desaulniers
2020-09-15 20:49 ` Borislav Petkov
2020-09-15 21:02 ` Josh Poimboeuf
2020-09-15 21:14 ` Borislav Petkov
2020-09-15 22:34 ` Nick Desaulniers
2020-09-16 7:03 ` Ilie Halip
2020-09-16 8:59 ` Marco Elver
2020-09-21 16:51 ` [tip: objtool/core] objtool: Ignore unreachable trap after call to noreturn functions tip-bot2 for Ilie Halip
2020-09-15 21:50 ` [tip:x86/seves] BUILD SUCCESS WITH WARNING e6eb15c9ba3165698488ae5c34920eea20eaa38e Arvind Sankar
2020-09-15 21:59 ` Nick Desaulniers
2020-09-15 22:44 ` Arvind Sankar
2020-09-16 11:34 ` Borislav Petkov
2020-09-16 18:28 ` Nick Desaulniers
2020-09-16 18:48 ` Borislav Petkov
2020-09-15 21:13 ` Nick Desaulniers
2020-09-15 21:28 ` Josh Poimboeuf
2020-09-15 23:35 ` Marco Elver
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200915172152.GR14436@zn.tnic \
--to=bp@alien8.de \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=ndesaulniers@google.com \
--cc=philip.li@intel.com \
--cc=rong.a.chen@intel.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.