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] Frama-c: WP issues

  • Subject: [Frama-c-discuss] Frama-c: WP issues
  • From: dmentre at (David MENTRE)
  • Date: Wed, 15 Jan 2014 17:39:58 +0100
  • In-reply-to: <B517F47C2F6D914AA8121201F9EBEE6701C76682DD39@Mail1.FCMD.local>
  • References: <B517F47C2F6D914AA8121201F9EBEE6701C76682DC29@Mail1.FCMD.local> <> <B517F47C2F6D914AA8121201F9EBEE6701C76682DD39@Mail1.FCMD.local>


Le 15/01/2014 17:35, Dharmalingam Ganesan a ?crit :
> According to a developer of alt-ergo (0.95), he thinks this behavior
> is valid for Oxygen (after he fixes syntax errors in the generated
> why/mlw code). This behavior is reported as unknown for the newest
> version Fluorine.

You should always use the latest version (currently Fluorine).

Have you applied my suggestion (adding asserts)? We cannot help you much 
without the code.

BTW, frama-c provides a C code obfuscator, it might be sufficient for 
you to provide the code.

Best regards,