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] bug with output to Alt-Ergo and CVC3
- Subject: [Frama-c-discuss] bug with output to Alt-Ergo and CVC3
- From: dak at adelard.com (Damien Karkinsky)
- Date: Thu, 07 Jan 2010 14:56:13 +0000
Hello, Consider the following: bool_t func1(float32_t x); /*@ ensures \result == TRUE */ bool_t func1(float32_t x) { if (x < 1E-6) { ; } return TRUE; } Alt-Ergo and CVC3 claim a syntax error on the input from Frama-C. I think its the constant expression 1E-6 that causes the problem. Are there any ways around this? Regards Damien
- Follow-Ups:
- [Frama-c-discuss] bug with output to Alt-Ergo and CVC3
- From: Pascal.CUOQ at cea.fr (CUOQ Pascal)
- [Frama-c-discuss] bug with output to Alt-Ergo and CVC3
- Prev by Date: [Frama-c-discuss] GWhy not working with Coq.
- Next by Date: [Frama-c-discuss] bug with output to Alt-Ergo and CVC3
- Previous by thread: [Frama-c-discuss] Jessie+Why 2.23+Gappa 0.12.3 unable to prove many binary_search VCs
- Next by thread: [Frama-c-discuss] bug with output to Alt-Ergo and CVC3
- Index(es):