From: Christopher Li <sparse@chrisli.org>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: Dave Jones <davej@redhat.com>, linux-sparse@vger.kernel.org
Subject: Re: sparse segfault on ppc64.
Date: Thu, 22 Mar 2007 15:16:12 -0700 [thread overview]
Message-ID: <20070322221612.GD22151@chrisli.org> (raw)
In-Reply-To: <20070322125911.GW4095@ftp.linux.org.uk>
On Thu, Mar 22, 2007 at 12:59:11PM +0000, Al Viro wrote:
> On Thu, Mar 22, 2007 at 12:03:54AM -0700, Christopher Li wrote:
> Humm... I don't see ppc segfaults with the current tree. However, after
> merging the mainline sparse changes and looking for regressions on kernel
> allmodconfig builds, I'm seeing a lot of noise due to expression_error() use.
> What used to generate a single error now brings a cascade. More often than
Can you show me some example of the duplicate error? I can't seem to hit it
in on x86. I do notice though there is a few context imbalance report on the
inline function instead of the caller site.
> not it's utterly pointless; actually, I can't find a single instance where
> additional errors would add any useful information...
The expression_error is not intend to report more error. It is try to avoid
test expr->ctype against zero all the time. We often have error path there is
some expression has NULL in ctype then sparse segfaulted.
We can work on clean up the duplicate warnings.
Chris
next prev parent reply other threads:[~2007-03-22 22:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 6:36 sparse segfault on ppc64 Dave Jones
2007-03-22 7:33 ` Al Viro
2007-03-22 7:03 ` Christopher Li
2007-03-22 12:59 ` Al Viro
2007-03-22 22:16 ` Christopher Li [this message]
2007-03-23 23:08 ` [PATCH] Fix the annotated inline call position Christopher Li
2007-04-20 10:09 ` Josh Triplett
2007-03-22 16:04 ` sparse segfault on ppc64 Dave Jones
2007-03-22 17:11 ` Dave Jones
2007-03-22 22:10 ` Christopher Li
2007-03-23 22:04 ` more spewage (Re: sparse segfault on ppc64) Randy Dunlap
2007-03-23 22:57 ` Christopher Li
2007-03-23 23:10 ` [PATCH] handle label attributes Christopher Li
2007-03-25 18:52 ` Randy Dunlap
2007-04-20 10:17 ` Josh Triplett
2007-03-23 23:31 ` more spewage (Re: sparse segfault on ppc64) Sam Ravnborg
2007-03-23 23:01 ` Christopher Li
2007-03-23 23:43 ` Randy Dunlap
2007-03-24 6:44 ` Sam Ravnborg
2007-03-24 16:46 ` Randy Dunlap
2007-03-24 17:02 ` Linus Torvalds
2007-03-26 18:07 ` Christopher Li
2007-03-26 18:50 ` Randy Dunlap
2007-03-22 15:56 ` sparse segfault on ppc64 Dave Jones
2007-03-22 16:02 ` Al Viro
2007-03-22 8:36 ` [PATCH] vector parsing, was " Christopher Li
2007-03-23 23:14 ` [PATCH] vector parsing (take II) Christopher Li
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=20070322221612.GD22151@chrisli.org \
--to=sparse@chrisli.org \
--cc=davej@redhat.com \
--cc=linux-sparse@vger.kernel.org \
--cc=viro@ftp.linux.org.uk \
/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).