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] Impact analysis: option/pragma and sub-code
- Subject: [Frama-c-discuss] Impact analysis: option/pragma and sub-code
- From: julien.signoles at cea.fr (Julien SIGNOLES)
- Date: Tue Nov 18 08:39:58 2008
- In-reply-to: <49226CCC.5000601@dassault-aviation.fr>
- References: <49226CCC.5000601@dassault-aviation.fr>
Hello Dillon, > It seems that > > -impact-pragma f1,...,fn : ... > ... > //@slice pragma stmt; : impact of the next statement > > should be replaced by: > > -impact-pragma f1,...,fn : ... > ... > //@impact pragma stmt; : impact of the next statement > Is it right? Yes it is. Fixed in the current CVS. > Current release of Impact Analysis provides us with "impacted" Statement > Ids as standard output. > Is it possible to get a compilable code instead (in batch mode)? Or > maybe is it in your future objectives? It is in my todo-list but without any planned agenda at this day. Many thanks for your report and your interest for the impact analysis, Julien
- References:
- [Frama-c-discuss] Impact analysis: option/pragma and sub-code
- From: dillon.pariente at dassault-aviation.fr (Dillon Pariente)
- [Frama-c-discuss] Impact analysis: option/pragma and sub-code
- Prev by Date: [Frama-c-discuss] Impact analysis: option/pragma and sub-code
- Next by Date: [Frama-c-discuss] type invariants
- Previous by thread: [Frama-c-discuss] Impact analysis: option/pragma and sub-code
- Next by thread: [Frama-c-discuss] type invariants
- Index(es):