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: dillon.pariente at dassault-aviation.fr (Dillon Pariente)
  • Date: Tue Nov 18 08:20:49 2008
Hello,

Two points about the Impact Analysis, used in batch mode on the current 
cvs release of Frama-C:

1?) Command line option

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
as slice pragma does not seem to be recognized by the analyzer.

Is it right?


2?) Sid vs compilable code

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?


Many thanks in advance for your answers.

Best regards,
Dillon Pariente