linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Ramsay Jones <ramsay@ramsayjones.plus.com>,
	Christopher Li <sparse@chrisli.org>,
	Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH 1/5] fix test for cast to bool on 32bit machines
Date: Mon, 27 Mar 2017 16:19:14 +0200	[thread overview]
Message-ID: <20170327141918.61151-2-luc.vanoostenryck@gmail.com> (raw)
In-Reply-To: <20170327141918.61151-1-luc.vanoostenryck@gmail.com>

The result implicitely depended on longs and/or pointers
being 64 bit or just bigger than ints.

Fix this by running the test with the -m64 flag.

Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
---
 validation/bool-cast-explicit.c | 2 +-
 validation/bool-cast-implicit.c | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/validation/bool-cast-explicit.c b/validation/bool-cast-explicit.c
index 6f9c4d461..4e3c2b7ce 100644
--- a/validation/bool-cast-explicit.c
+++ b/validation/bool-cast-explicit.c
@@ -16,7 +16,7 @@ static _Bool fres(le16 a) { return (_Bool)a; }
 
 /*
  * check-name: bool-cast-explicit
- * check-command: test-linearize $file
+ * check-command: test-linearize -m64 $file
  * check-output-ignore
  * check-output-excludes: cast\\.
  *
diff --git a/validation/bool-cast-implicit.c b/validation/bool-cast-implicit.c
index 0e0e69a45..ee8b705b9 100644
--- a/validation/bool-cast-implicit.c
+++ b/validation/bool-cast-implicit.c
@@ -16,7 +16,7 @@ static _Bool fres(le16 a) { return a; }
 
 /*
  * check-name: bool-cast-implicit
- * check-command: test-linearize $file
+ * check-command: test-linearize -m64 $file
  * check-output-ignore
  * check-output-excludes: cast\\.
  *
-- 
2.12.0


  reply	other threads:[~2017-03-27 14:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-27 14:19 [PATCH 0/5] fix test cases on 32bit Luc Van Oostenryck
2017-03-27 14:19 ` Luc Van Oostenryck [this message]
2017-03-27 14:19 ` [PATCH 2/5] predefine __INT_MAX__ and friends Luc Van Oostenryck
2017-03-27 14:19 ` [PATCH 3/5] predefine __SIZEOF_INT__ & friends Luc Van Oostenryck
2017-03-27 14:19 ` [PATCH 4/5] fix test validation/div.c Luc Van Oostenryck
2017-03-27 14:19 ` [PATCH 5/5] do not depends on limits.h to test __CHAR_BIT__ Luc Van Oostenryck
2017-04-01 10:32 ` [GIT PULL] fix test cases on 32bit Luc Van Oostenryck

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=20170327141918.61151-2-luc.vanoostenryck@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).