lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 19 Oct 2014 11:46:29 +0200
From:	Mariusz Gorski <>
Subject: Sparse warning: "initializer entry defined twice" - sparse can't
 handle bool?

Sparse throws the following warning, which I can't really understand:

$ make drivers/staging/vt6655/ C=2
  CHECK   drivers/staging/vt6655/datarate.c
drivers/staging/vt6655/datarate.c:302:40: warning: Initializer entry
defined twice
drivers/staging/vt6655/datarate.c:302:46:   also defined here

The code looks fine to me:
bool bAutoRate[MAX_RATE]    = {true, true, true, true, false, false,
true, true, true, true, true, true};

I've googled it and found only this LKML discussion:

I've tested the suggested code sample and here are the results:
$ cat foo.c
typedef _Bool bool;
enum {
     false = 0,
     true = 1
static const bool foo[10] = {

$ sparse foo.c
foo.c:7:8: warning: Initializer entry defined twice
foo.c:8:8:   also defined here

It this a sparse problem?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists