Linux SPARSE checker discussions
 help / color / mirror / Atom feed
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 19:15:05 +0200	[thread overview]
Message-ID: <20170327171504.jsj3yez4r5doha3r@macpro.local> (raw)
In-Reply-To: <b3629c23-28e6-370d-0716-787e34a8f854@ramsayjones.plus.com>

On Mon, Mar 27, 2017 at 05:53:17PM +0100, Ramsay Jones wrote:
> 
> > OK, thanks.
> > It should be OK as I new tested it on a 32bit machine but
> > another environment is always good for testing.
> 
> OK, so I tested the 5 patch series + the v2 patch that you sent
> out on Linux 64bit, Linux 32bit and cygwin 64bit.
> 
> I applied the patches on top of the current 'sparse-next' branch:
> 
>   $ git branch -v
>     chrisl-master   ce18a90 sparse: update __builtin_object_size() prototype
>     master          fbbfc73 simplify float-to-float casts that doesn't change size
>     mingw           9e96dd5 test-suite: Add -b option to ignore CR at eol on MinGW
>     sparse-next     f7817f0 llvm: cleanup of output_[ptr]cast()
>   * sparse-next-tmp df7cd04 fix expansion of integers to floats
> 
>   $ git log --oneline sparse-next..
>   df7cd04 fix expansion of integers to floats
>   83de8c4 do not depends on limits.h to test __CHAR_BIT__
>   ac9f7b4 fix test validation/div.c
>   153d5cf predefine __SIZEOF_INT__ & friends
>   a3a916c predefine __INT_MAX__ and friends
>   26a0a0a fix test for cast to bool on 32bit machines
>   $ 
> 
> On Linux 64bit, I get:
> 
>   $ make check
>   ...
>   Out of 214 tests, 205 passed, 9 failed (9 of them are known to fail)
>   39 tests were disabled
>   $ 
> 
> On Linux 32bit, I get:
> 
>   $ make check
>   ...
>        TEST     call-inlined (call-inlined.c)
>   error: actual output text does not match expected output text.
>   error: see call-inlined.c.output.* for further investigation.
>   --- call-inlined.c.output.expected	2017-03-27 16:57:23.438683323 +0100
>   +++ call-inlined.c.output.got	2017-03-27 16:57:23.442685323 +0100

Yes, this is expected. Sorry, I should have told earlier.
Those were part of another serie that I didn't yes sent an updated
version. The 5 patches series only covered what's already in master,
not sparse-next.

I'll sent an updated version for what's in sparse-next a bit later.

-- Luc

  reply	other threads:[~2017-03-27 17:25 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
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 [this message]
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=20170327171504.jsj3yez4r5doha3r@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