From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Ramsay Jones <ramsay@ramsayjones.plus.com>
Cc: Christopher Li <sparse@chrisli.org>,
Sparse Mailing-list <linux-sparse@vger.kernel.org>
Subject: Re: extra 'make check' failures on 32bit Linux
Date: Mon, 27 Mar 2017 03:03:43 +0200 [thread overview]
Message-ID: <20170327010342.vd34svh3kee43qir@macpro.local> (raw)
In-Reply-To: <806988fb-6e3c-872b-d7ab-282336f67f73@ramsayjones.plus.com>
On Sun, Mar 26, 2017 at 11:21:44PM +0100, Ramsay Jones wrote:
> Hi Christopher, Luc,
>
> On occasion I build sparse on 32-bit Linux and I have noticed, for some
> weeks now, unexpected test failures. I have been meaning to take a look
> at fixing these failures, but I just haven't had the time ... :(
> ...
>
> TEST division constants (div.c)
> error: actual error text does not match expected error text.
> error: see div.c.error.* for further investigation.
> --- div.c.error.expected 2017-03-26 18:26:04.142887258 +0100
> +++ div.c.error.got 2017-03-26 18:26:04.142887258 +0100
> @@ -2,8 +2,6 @@
> div.c:4:20: warning: division by zero
> div.c:5:22: warning: division by zero
> div.c:7:25: warning: constant integer operation overflow
> -div.c:8:27: warning: constant integer operation overflow
> div.c:9:34: warning: constant integer operation overflow
> div.c:11:25: warning: constant integer operation overflow
> -div.c:12:27: warning: constant integer operation overflow
> div.c:13:34: warning: constant integer operation overflow
> ...
It's not very clear to me what is the cause of this error.
Have you only since some weeks (then I think it's since the
we define __SIZEOF_POINTER__) or is it older (then I think
it exists since quite a long time)?
-- Luc
next prev parent reply other threads:[~2017-03-27 1:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-26 22:21 extra 'make check' failures on 32bit Linux Ramsay Jones
2017-03-26 23:56 ` Luc Van Oostenryck
2017-03-27 1:03 ` Luc Van Oostenryck [this message]
2017-03-27 15:27 ` Ramsay Jones
2017-03-27 16:10 ` Luc Van Oostenryck
2017-03-27 16:53 ` Ramsay Jones
2017-03-27 17:15 ` Luc Van Oostenryck
2017-03-27 7:51 ` 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=20170327010342.vd34svh3kee43qir@macpro.local \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=ramsay@ramsayjones.plus.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox