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] A small plugin to specific which coq strategy to use per block annotation

  • Subject: [Frama-c-discuss] A small plugin to specific which coq strategy to use per block annotation
  • From: Pierre-Loic.Garoche at (Pierre-Loïc Garoche)
  • Date: Tue, 12 Mar 2013 17:23:41 +0100

Hi everybody,

I just committed a plugin that allows to specify for code annotations (spec of blocks) which coq strategy to apply. I hope it can be useful for some of you.

Strategies should be declared as ACSL terms and you should declare the predicate use_strategy:

/*@ axiomatic ellipsoids_proof_tactics {
  @   type ellipsoids_tactics = Intuition | Tactic2;
  @   predicate use_strategy (ellipsoids_tactics t);
  @ }

Then each block specification can use the following grammar extension:

/*@ requires x < 0;
  @ ensures \result <= 0; 
int plus_one (int x) {
int y,z;
/*@ ensures y <= 0; 
  @ PROOF_TACTIC (use_strategy (Intuition));
y = x + 1;
/*@ ensures z <= 0; 
  @ PROOF_TACTIC (use_strategy (Tactic2));
z = 2 * y;
return z;

The plugin will call WP on each of those block annotations and update the default coq strategy with the specified proof tactic.


For the moment only block specification are concerned and *not* function specifications.


Pierre-Lo?c Garoche
Research Scientist @ ONERA
pierre-loic.garoche at - pierre-loic-garoche at
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <>