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] [PROVENANCE INTERNET] Re: I wrote a blog post about my experiences with Frama-C so far

See also (automatic path-test generation with the PathCrawler plugin to
MEASURE worst-case execution time):

http://pathcrawler-online.com:8080/pubs/ast09researchcopy.pdf


On 26/11/2018 12:54, François Bobot wrote:
> Le 26/11/2018 à 12:31, Tomas Härdin a écrit :
>>> By the way, you say in your post:
>>>> Frama-C is not a panacea, since it says nothing about how long a
>>>> program might take to execute.
>>>  In fact, some research work has been done on that topic:
>>>  Certifying and Reasoning on Cost Annotations in C Programs 
>>>  https://link.springer.com/chapter/10.1007%2F978-3-642-32469-7_3
>> Neat. Can't access the paper, sadly.
> It is accessible here:
>   https://hal.inria.fr/hal-00702665v2/document
>
> A broader overview of the project is available here
> Certified complexity (cerco):
>   http://cerco.cs.unibo.it/export/3340/Papers/fopara2013/fopara13.pdf
>
>
> But the simplifying part is that is is applied to a 8051 processor which doesn't have pipeline and
> cache.
>
> Best,
>