From: Jiri Slaby <jirislaby@gmail.com>
To: linux-sparse@vger.kernel.org
Subject: rewrite_parent_branch: Assertion `changed' failed
Date: Mon, 07 Apr 2008 20:53:35 +0200 [thread overview]
Message-ID: <47FA6DAF.3030600@gmail.com> (raw)
Hi,
I got this from sparse:
CHECK /home/l/latest/xxx/net/mac80211/ieee80211.c
sparse: flow.c:804: rewrite_parent_branch: Assertion `changed' failed.
/bin/sh: line 1: 8639 Neúspěšně ukončen (SIGABRT) sparse -D__linux__
-Dlinux -D__STDC__ -Dunix -D__unix__ -Wbitwise -D__x86_64__ -m64 -nostdinc
-isystem /usr/lib64/gcc/x86_64-suse-linux/4.2.1/include
-Wp,-MD,net/mac80211/.ieee80211.o.d -nostdinc -isystem
/usr/lib64/gcc/x86_64-suse-linux/4.2.1/include -D__KERNEL__ -Iinclude -Iinclude2
-I/home/l/latest/xxx/include -include include/linux/autoconf.h
-I/home/l/latest/xxx/net/mac80211 -Inet/mac80211 -Wall -Wundef
-Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common
-Werror-implicit-function-declaration -O2 -fno-stack-protector -m64
-mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time
-maccumulate-outgoing-args -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1
-pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mno-sse -mno-mmx
-mno-sse2 -mno-3dnow -fno-omit-frame-pointer -fno-optimize-sibling-calls -g
-Wdeclaration-after-statement -Wno-pointer-sign -DMODULE -D"KBUILD_STR(s)=#s"
-D"KBUILD_BASENAME=KBUILD_STR(ieee80211)"
-D"KBUILD_MODNAME=KBUILD_STR(mac80211)" /home/l/latest/xxx/net/mac80211/ieee80211.c
make[3]: *** [net/mac80211/ieee80211.o] Error 134
make[2]: *** [net/mac80211] Error 2
make[1]: *** [net] Error 2
make: *** [sub-make] Error 2
--
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
next reply other threads:[~2008-04-07 18:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 18:53 Jiri Slaby [this message]
2008-04-07 19:05 ` rewrite_parent_branch: Assertion `changed' failed Jiri Slaby
2008-04-07 21:22 ` Pavel Roskin
2008-04-07 21:29 ` Jiri Slaby
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=47FA6DAF.3030600@gmail.com \
--to=jirislaby@gmail.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).