All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil@xs4all.nl>
To: Christopher Li <sparse@chrisli.org>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: Bogus 'Initializer entry defined twice' warnings
Date: Fri, 05 Dec 2014 14:39:12 +0100	[thread overview]
Message-ID: <5481B580.3080100@xs4all.nl> (raw)
In-Reply-To: <CANeU7Q=q7AL=nh2BGfHyAYqjHbMu9cu3NbR7Jkfw4wd+SPRWUA@mail.gmail.com>

Hi Chris,

On 11/12/2014 04:39 PM, Christopher Li wrote:
> On Fri, Aug 29, 2014 at 4:10 PM, Hans Verkuil <hverkuil@xs4all.nl> wrote:
>> The following test source (based on drivers/media/pci/cx88/cx88-cards.c from
>> the kernel) gives these sparse warnings:
>>
>> cards4.c:447:36: warning: Initializer entry defined twice
>> cards4.c:449:19:   also defined here
>>
>> I am using the latest sparse code from
>> git://git.kernel.org/pub/scm/devel/sparse/chrisl/sparse.git.
> 
> Thanks for the bug report. It has been puzzling for me as well.
> It seems there is some duplicate entry in the expression list
> for the very long initializer. The duplicate entry first show up after
> the expand_symbol phase. The bug will disappear if the list is
> sorter.
> 
> I have narrow it down to the sort_list() function.
> If we turn on " #define PARANOIA" in sort.c.
> Sparse can trigger assert fail:
> 
> sparse: sort.c:89: verify_seq_sorted: Assertion `cmp (a, b) <= 0' failed.
> Aborted (core dumped)
> 
> Still need more work to fix it.

Any updates on this?

Thanks,

	Hans

> 
> Chris
> --
> 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:[~2014-12-05 13:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-29  8:10 Bogus 'Initializer entry defined twice' warnings Hans Verkuil
2014-11-05  7:44 ` Hans Verkuil
2014-11-05 10:49   ` Christopher Li
2014-11-12 15:39 ` Christopher Li
2014-12-05 13:39   ` Hans Verkuil [this message]
2014-12-09  1:11     ` Christopher Li
2014-12-12  4:32     ` Christopher Li
2014-12-12  8:04       ` Hans Verkuil
2014-12-12  8:12       ` Josh Triplett

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=5481B580.3080100@xs4all.nl \
    --to=hverkuil@xs4all.nl \
    --cc=linux-sparse@vger.kernel.org \
    --cc=sparse@chrisli.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.