Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • F frama-c
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 204
    • Issues 204
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • pub
  • frama-c
  • Issues
  • #506
Closed
Open
Created Jan 26, 2016 by Jens Gerlach@gerlach

LoopEntry vs LoopInit

ID0002203: This issue was created automatically from Mantis Issue 2203. Further discussion may take place here.


Id Project Category View Due Date Updated
ID0002203 Frama-C Documentation > ACSL public 2016-01-26 2016-06-21
Reporter jens Assigned To virgile Resolution fixed
Priority high Severity text Reproducibility always
Platform - OS - OS Version -
Product Version Frama-C Magnesium Target Version - Fixed in Version Frama-C Aluminium

Description :

In Example 2.30 (Page 43) of the ACSL implementation document (for both Magnesium and Sodium) the code snippet uses the label "LoopInit". I think "LoopEntry" is meant.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking