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] Plugins in next Frama-C?

  • Subject: [Frama-c-discuss] Plugins in next Frama-C?
  • From: pascal.cuoq at gmail.com (Pascal Cuoq)
  • Date: Wed, 6 Oct 2010 12:37:47 -0700
  • In-reply-to: <AANLkTikw8pjgcE3LS1tqDebwktuECBkoFfLLRAw=UEFu@mail.gmail.com>
  • References: <AANLkTikw8pjgcE3LS1tqDebwktuECBkoFfLLRAw=UEFu@mail.gmail.com>
> Regarding the next version of Frama-C, are any changes planned in the
> set of plug-ins (addition, deprecation, major change in a plug-in)?

The value analysis will require much less memory for many large
analyses, along with other less striking improvements. The ratios
range from 4 to 100 for the existing memory consumption benchmarks
that I had lying around (that is, from 4 times less memory required to
100 times less memory required).

External plug-in implementors will discover a new API for defining
datatypes, along with an almost automatic transition script for
existing external plug-ins.

There will be a new weakest precondition plug-in alongside Jessie,
with different strengths and weaknesses. It will of course make use of
the same ACSL contracts.

Note that no date is fixed for a Carbon release and that while it is
unlikely that these changes do not happen, many others could be added
to the list in the meantime.

Pascal