Frama-C-discuss mailing list archives

This page gathers the archives of the old Frama-C-discuss archives, that was hosted by Inria's gforge before its demise at the end of 2020. To search for mails newer than September 2020, please visit the page of the new mailing list on Renater.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Frama-c-discuss] [wp] type conversion check is less strict than Jessie?

  • Subject: [Frama-c-discuss] [wp] type conversion check is less strict than Jessie?
  • From: x_cui at hotmail.com (Xiao-lei Cui)
  • Date: Mon, 9 Dec 2013 01:02:57 -0500
Hi all,
   I used Jessie plug-in before I tried wp.   
   Jessie will not tolerate the following situation where a int constant is to be converted to unsigned int*
--------------------------------------------------------------
#define ARTAR                ( (unsigned int * )0x01f800e0) )
unsigned int  sr;
sr = ARTAR;    
--------------------------------------------------------------
[jessie] failure: Casting from type int to type struct unsigned_intP * not allowed

However, as I run wp plug-in over the same C file:
$ frama-c  -pp-annot  -wp -wp-rte -wp-prover why3ide file.c

I did not get any complaints from wp, and the VCs( very simple though) seems proved already:
[wp] Running WP plugin...
[wp] Collecting axiomatic usage
[rte] annotating function SerialBaud
[wp] Goal typed_SB_b1_post : trivial
[wp] Goal typed_SB_b2_post : trivial

Jessie and WP behaves so differently in type conversion check (for this case) ? Is it that type check is turned off by default in WP? or I did not invoke wp in the correct way..

Any hints would be appreciated. Thanks..

cheers
xiao-lei


 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gforge.inria.fr/pipermail/frama-c-discuss/attachments/20131209/08fa322e/attachment.html>