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] Standard C library specifications in the wild
- Subject: [Frama-c-discuss] Standard C library specifications in the wild
- From: androlivem at gmail.com (Andre Oliveira)
- Date: Wed, 18 Mar 2015 19:55:45 +0100
Dear all, It has been mentioned during the Frama-C day that better ACSL specifications concerning the standard C library would be useful to the platform. I would like to find out about existing public repositories with such specifications, to have an idea of the kind of specifications that are used, and also their level of detail. An example would be kLIBC, a subset of the C standard library with an annotated implementation. I am also interested in pure specifications, without an underlying implementation. Regards, Andr? Oliveira -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gforge.inria.fr/pipermail/frama-c-discuss/attachments/20150318/e60b6569/attachment.html>
- Follow-Ups:
- [Frama-c-discuss] Standard C library specifications in the wild
- From: dcok at grammatech.com (David R. Cok)
- [Frama-c-discuss] Standard C library specifications in the wild
- Prev by Date: [Frama-c-discuss] Sodium release
- Next by Date: [Frama-c-discuss] Astraver Toolset 1.0
- Previous by thread: [Frama-c-discuss] Sodium release
- Next by thread: [Frama-c-discuss] Standard C library specifications in the wild
- Index(es):