linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Christopher Li" <sparse@chrisli.org>
To: Dave Jones <davej@redhat.com>
Cc: linux-sparse@vger.kernel.org
Subject: Re: assertion when running sparse on current linux.git
Date: Wed, 7 Nov 2007 12:25:01 -0800	[thread overview]
Message-ID: <70318cbf0711071225v5357edd5hebb2b7eeacfcc524@mail.gmail.com> (raw)
In-Reply-To: <20071107175847.GA19586@redhat.com>

Looks like the local label problem which is already fixed in tip of sparse git.

Have you try the sparse git tree?

Chris

On Nov 7, 2007 9:58 AM, Dave Jones <davej@redhat.com> wrote:
> $ make kernel/sched.o C=1
>   CHK     include/linux/version.h
>   CHK     include/linux/utsrelease.h
>   CALL    scripts/checksyscalls.sh
>   CHECK   kernel/sched.c
> kernel/sched_idletask.c:69:26: warning: symbol 'idle_sched_class' was not declared. Should it be static?
> kernel/sched_rt.c:239:26: warning: symbol 'rt_sched_class' was not declared. Should it be static?
> kernel/sched.c:1885:17: warning: symbol 'schedule_tail' was not declared. Should it be static?
> kernel/sched.c:3616:15: warning: incorrect type in assignment (different signedness)
> kernel/sched.c:3616:15:    expected long *switch_count
> kernel/sched.c:3616:15:    got unsigned long *<noident>
> kernel/sched.c:3638:16: warning: incorrect type in assignment (different signedness)
> kernel/sched.c:3638:16:    expected long *switch_count
> kernel/sched.c:3638:16:    got unsigned long *<noident>
> kernel/sched.c:5624:12: warning: symbol 'migration_init' was not declared. Should it be static?
> kernel/sched.c:5841:25: error: cannot size expression
> sparse: flow.c:805: rewrite_parent_branch: Assertion `changed' failed.
> /bin/sh: line 1: 19800 Aborted                 sparse -D__linux__ -Dlinux -D__STDC__ -Dunix -D__unix__ -Wbitwise -D__x86_64__ -m64 -nostdinc -isystem /usr/lib/gcc/x86_64-redhat-linux/4.1.2/include -Wp,-MD,kernel/.sched.o.d -nostdinc -isystem /usr/lib/gcc/x86_64-redhat-linux/4.1.2/include -D__KERNEL__ -Iinclude -include include/linux/autoconf.h -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Os -mtune=generic -m64 -mno-red-zone -mcmodel=kernel -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -funit-at-a-time -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -maccumulate-outgoing-args -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -fstack-protector -fomit-frame-pointer -g -fno-stack-protector -Wdeclaration-after-stateme
 nt -Wno-pointer-sign -fno-omit-frame-pointer -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(sched)" -D"KBUILD_MODNAME=KBUILD_STR(sched)" kernel/sched.c
> make[1]: *** [kernel/sched.o] Error 134
> make: *** [kernel/sched.o] Error 2
>
>
>
>         Dave
>
> --
> http://www.codemonkey.org.uk
> -
> To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

  reply	other threads:[~2007-11-07 20:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-07 17:58 assertion when running sparse on current linux.git Dave Jones
2007-11-07 20:25 ` Christopher Li [this message]
2007-11-07 21:14   ` Dave Jones

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=70318cbf0711071225v5357edd5hebb2b7eeacfcc524@mail.gmail.com \
    --to=sparse@chrisli.org \
    --cc=davej@redhat.com \
    --cc=linux-sparse@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).