2004-09-09 14:57:54

by John Cherry

[permalink] [raw]
Subject: 10 New compile/sparse warnings (overnight build)


Summary:
New warnings = 10
Fixed warnings = 2

New warnings:
-------------
net/ipv4/ipconfig.c:969:10: warning: undefined identifier 'i'
net/ipv4/ipconfig.c:969:10: warning: generating address of non-lvalue

net/ipv4/ipconfig.c:969:10: warning: undefined identifier 'i'
net/ipv4/ipconfig.c:969:10: warning: generating address of non-lvalue

net/ipv4/ipconfig.c:969:32: warning: undefined identifier 'i'

net/ipv4/ipconfig.c:969:39: warning: unknown expression (7 46)

net/ipv4/ipconfig.c:970:18: warning: unknown expression (7 46)

net/ipv4/ipconfig.c:970:31: warning: undefined identifier 'i'
net/ipv4/ipconfig.c:970:31: warning: generating address of non-lvalue
net/ipv4/ipconfig.c:970:31: warning: loading unknown expression

net/ipv4/ipconfig.c:970:31: warning: undefined identifier 'i'
net/ipv4/ipconfig.c:970:31: warning: generating address of non-lvalue
net/ipv4/ipconfig.c:970:31: warning: loading unknown expression

net/ipv4/ipconfig.c:970:31: warning: undefined identifier 'i'
net/ipv4/ipconfig.c:970:31: warning: generating address of non-lvalue
net/ipv4/ipconfig.c:970:31: warning: loading unknown expression

net/ipv4/ipconfig.c:971:16: warning: unknown expression (7 46)

net/ipv4/ipconfig.c:971:9: warning: undefined identifier 'i'


Fixed warnings:
---------------
fs/coda/file.c:298:14: warning: incorrect type in initializer
(incompatible argument 5 (different address spaces))
fs/coda/file.c:298:14: expected int [usertype] ( *sendfile )( ... )
fs/coda/file.c:298:14: got int [usertype] ( static [addressable]
[toplevel] *<noident> )( ... )

fs/coda/file.c:61:66: warning: incorrect type in argument 5 (different
address spaces)
fs/coda/file.c:61:66: expected void *<noident>
fs/coda/file.c:61:66: got void [noderef] *target<asn:1>




2004-09-09 16:43:47

by John Cherry

[permalink] [raw]
Subject: Re: 10 New compile/sparse warnings (overnight build)

Sorry about the duplicate entries. I'll fix the tool. There are really
just 7 new sparse warnings.

John

On Thu, 2004-09-09 at 07:57, John Cherry wrote:
> Summary:
> New warnings = 10
> Fixed warnings = 2
>
> New warnings:
> -------------
> net/ipv4/ipconfig.c:969:10: warning: undefined identifier 'i'
> net/ipv4/ipconfig.c:969:10: warning: generating address of non-lvalue
>
> net/ipv4/ipconfig.c:969:10: warning: undefined identifier 'i'
> net/ipv4/ipconfig.c:969:10: warning: generating address of non-lvalue
>
> net/ipv4/ipconfig.c:969:32: warning: undefined identifier 'i'
>
> net/ipv4/ipconfig.c:969:39: warning: unknown expression (7 46)
>
> net/ipv4/ipconfig.c:970:18: warning: unknown expression (7 46)
>
> net/ipv4/ipconfig.c:970:31: warning: undefined identifier 'i'
> net/ipv4/ipconfig.c:970:31: warning: generating address of non-lvalue
> net/ipv4/ipconfig.c:970:31: warning: loading unknown expression
>
> net/ipv4/ipconfig.c:970:31: warning: undefined identifier 'i'
> net/ipv4/ipconfig.c:970:31: warning: generating address of non-lvalue
> net/ipv4/ipconfig.c:970:31: warning: loading unknown expression
>
> net/ipv4/ipconfig.c:970:31: warning: undefined identifier 'i'
> net/ipv4/ipconfig.c:970:31: warning: generating address of non-lvalue
> net/ipv4/ipconfig.c:970:31: warning: loading unknown expression
>
> net/ipv4/ipconfig.c:971:16: warning: unknown expression (7 46)
>
> net/ipv4/ipconfig.c:971:9: warning: undefined identifier 'i'
>
>
> Fixed warnings:
> ---------------
> fs/coda/file.c:298:14: warning: incorrect type in initializer
> (incompatible argument 5 (different address spaces))
> fs/coda/file.c:298:14: expected int [usertype] ( *sendfile )( ... )
> fs/coda/file.c:298:14: got int [usertype] ( static [addressable]
> [toplevel] *<noident> )( ... )
>
> fs/coda/file.c:61:66: warning: incorrect type in argument 5 (different
> address spaces)
> fs/coda/file.c:61:66: expected void *<noident>
> fs/coda/file.c:61:66: got void [noderef] *target<asn:1>
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/

2004-09-09 17:37:30

by Dave Jones

[permalink] [raw]
Subject: Re: 10 New compile/sparse warnings (overnight build)

On Thu, Sep 09, 2004 at 09:39:27AM -0700, John Cherry wrote:
> Sorry about the duplicate entries. I'll fix the tool. There are really
> just 7 new sparse warnings.

Out of curiosity, how often is the sparse binary being updated
in this automated check ?

Dave

2004-09-09 18:29:48

by John Cherry

[permalink] [raw]
Subject: Re: 10 New compile/sparse warnings (overnight build)

The sparse binary is being updated every two weeks. I am trying to
avoid mining reasonable data with a changing kernel AND a changing
sparse tool.

John

On Thu, 2004-09-09 at 10:29, Dave Jones wrote:
> On Thu, Sep 09, 2004 at 09:39:27AM -0700, John Cherry wrote:
> > Sorry about the duplicate entries. I'll fix the tool. There are really
> > just 7 new sparse warnings.
>
> Out of curiosity, how often is the sparse binary being updated
> in this automated check ?
>
> Dave