From: Randy Dunlap <rdunlap@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: Re: Linux 5.9-rc1 (sparse? kernel/time/timekeeping.c)
Date: Sun, 16 Aug 2020 18:35:26 -0700 [thread overview]
Message-ID: <83b35552-d1a2-e4ce-9a41-2b5cf688ccf0@infradead.org> (raw)
In-Reply-To: <CAHk-=wiwfkKp93C+yLqKWAU0ChBdeBDUhgOk09_=UQ8gOKbV3w@mail.gmail.com>
On 8/16/20 1:50 PM, Linus Torvalds wrote:
> This merge window felt a lot more normal than 5.8, and all the stats
> confirm thar it seems to be the usual size.
>
on x86_64, allmodconfig:
$ gcc --version
gcc (SUSE Linux) 7.5.0
$ sparse --version
0.6.2
I seem to be having some problems with kernel/time/timekeeping.c,
including a segfault.
a. Is it sparse that segfaults?
b. what prints this message?
make[3]: *** Deleting file 'kernel/time/timekeeping.o'
c. I would prefer to be able to tell the source of warning/error messages,
i.e., gcc or sparse. Especially when they are intermixed.
So one solution IMO would be to be able to do a full sparse check _only_,
without the gcc build. That way the messages would obviously be from sparse.
Another reason to do that is that I often do gcc builds and then would like
to follow that up with a sparse check build, but currently that means that
I have to do the full gcc + sparse build, which is really time consuming
since I have a wimpy laptop.
CC kernel/time/timekeeping.o
CHECK ../kernel/time/timekeeping.c
../kernel/time/timekeeping.c:461:23: warning: trying to copy expression type 31
../kernel/time/timekeeping.c:470:18: warning: trying to copy expression type 31
../include/linux/seqlock.h:214:1: warning: unreplaced symbol 's'
../include/linux/seqlock.h:214:1: warning: unreplaced symbol 'return'
../kernel/time/timekeeping.c:461:23: warning: unreplaced symbol 's'
../kernel/time/timekeeping.c:461:23: warning: unreplaced symbol 'return'
../include/linux/seqlock.h:214:1: warning: unreplaced symbol 's'
../include/linux/seqlock.h:214:1: warning: unreplaced symbol 'return'
../kernel/time/timekeeping.c:470:18: warning: unreplaced symbol 's'
../kernel/time/timekeeping.c:470:18: warning: unreplaced symbol 'return'
/bin/sh: line 1: 15126 Segmentation fault (core dumped) sparse -D__linux__ -Dlinux -D__STDC__ -Dunix -D__unix__ -Wbitwise -Wno-return-void -Wno-unknown-attribute -D__x86_64__ --arch=x86_64 -mlittle-endian -m64 -Wp,-MMD,kernel/time/.timekeeping.o.d -nostdinc -isystem /usr/lib64/gcc/x86_64-suse-linux/7/include -I../arch/x86/include -I./arch/x86/include/generated -I../include -I./include -I../arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I../include/uapi -I./include/generated/uapi -include ../include/linux/kconfig.h -include ../include/linux/compiler_types.h -D__KERNEL__ -Wall -Wundef -Werror=strict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -fno-PIE -Werror=implicit-function-declaration -Werror=implicit-int -Wno-format-security -std=gnu89 -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -DCONFIG_X86_X32_ABI -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -fno-jump-tables -fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno-format-overflow -O2 --param=allow-store-data-races=0 -fno-reorder-blocks -fno-ipa-cp-clone -fno-partial-inlining -Wframe-larger-than=2048 -fstack-protector-strong -Wno-unused-but-set-variable -Wimplicit-fallthrough -Wno-unused-const-variable -fno-var-tracking-assignments -pg -mrecord-mcount -mfentry -DCC_USING_FENTRY -fno-inline-functions-called-once -flive-patching=inline-clone -falign-functions=32 -Wdeclaration-after-statement -Wvla -Wno-pointer-sign -Wno-array-bounds -Wno-stringop-overflow -Wno-restrict -Wno-maybe-uninitialized -fno-strict-overflow -fno-merge-all-constants -fmerge-constants -fno-stack-check -fconserve-stack -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -fsanitize-coverage=trace-pc -I ../kernel/time -I ./kernel/time -DKBUILD_MODFILE='"kernel/time/timekeeping"' -DKBUILD_BASENAME='"timekeeping"' -DKBUILD_MODNAME='"timekeeping"' ../kernel/time/timekeeping.c
make[3]: *** [../scripts/Makefile.build:283: kernel/time/timekeeping.o] Error 139
make[3]: *** Deleting file 'kernel/time/timekeeping.o'
make[3]: *** Waiting for unfinished jobs....
thanks.
--
~Randy
next prev parent reply other threads:[~2020-08-17 1:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-16 20:50 Linux 5.9-rc1 Linus Torvalds
2020-08-16 22:58 ` Re:..build stopped... " Bhaskar Chowdhury
2020-08-17 16:44 ` ..build " Linus Torvalds
2020-08-17 21:25 ` .config file attached for your perusal..build " Bhaskar Chowdhury
2020-08-17 23:22 ` Randy Dunlap
2020-08-17 23:32 ` Linus Torvalds
2020-08-18 0:43 ` Bhaskar Chowdhury
2020-08-17 1:35 ` Randy Dunlap [this message]
2020-08-17 2:15 ` Linux 5.9-rc1 (sparse? kernel/time/timekeeping.c) Luc Van Oostenryck
2020-08-17 2:17 ` Randy Dunlap
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=83b35552-d1a2-e4ce-9a41-2b5cf688ccf0@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®