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] -metrics discrepency Boron/Nitrogen
- Subject: [Frama-c-discuss] -metrics discrepency Boron/Nitrogen
- From: richard.bonichon at gmail.com (Richard Bonichon)
- Date: Mon, 14 May 2012 11:05:32 +0200
- In-reply-to: <20120514084638.GA6128@opentech.at>
- References: <20120514084638.GA6128@opentech.at>
Hi Nicholas, This seems to be a bug in Boron. It should be noted that the metrics plug-in has changed quite a lot since then. As explained in the plug-in's manual (section 1.1.2), most Frama-c analyses are done on an internal normalized abstract syntax tree produce by CIL. The "unexpected" goto comes from this normalization. You can see a concrete represenataion of both ASTs using Frama-c's GUI. Cheers, -- Richard Bonichon -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gforge.inria.fr/pipermail/frama-c-discuss/attachments/20120514/be30c811/attachment.html>
- Follow-Ups:
- [Frama-c-discuss] -metrics discrepency Boron/Nitrogen
- From: richard.bonichon at gmail.com (Richard Bonichon)
- [Frama-c-discuss] -metrics discrepency Boron/Nitrogen
- References:
- [Frama-c-discuss] -metrics discrepency Boron/Nitrogen
- From: der.herr at hofr.at (Nicholas Mc Guire)
- [Frama-c-discuss] -metrics discrepency Boron/Nitrogen
- Prev by Date: [Frama-c-discuss] -metrics discrepency Boron/Nitrogen
- Next by Date: [Frama-c-discuss] training course Frama-C runtime-error detection 5&6 july Tlse
- Previous by thread: [Frama-c-discuss] -metrics discrepency Boron/Nitrogen
- Next by thread: [Frama-c-discuss] -metrics discrepency Boron/Nitrogen
- Index(es):