Skip to content
GitLab
Projects Groups Topics 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
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 168
    • Issues 168
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
    • Model experiments
  • 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
  • #2248

Problems parsing hex in pragmas

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


Id Project Category View Due Date Updated
ID0000696 Frama-C Kernel public 2011-01-28 2011-01-28
Reporter djs52 Assigned To - Resolution won't fix
Priority normal Severity minor Reproducibility always
Platform - OS - OS Version -
Product Version Frama-C Carbon-20101202-beta2 Target Version - Fixed in Version -

Description :

I am working with some source code which uses pragmas to set the absolute storage locations of variables, of the form

#pragma ADDRESS var 0c1h

Mostly, this is accepted by Frama-C, however certain cases are not, such as

#pragma ADDRESS var 0e1h

The problem cases all seem to include the hex digit 'e' followed by a digit 0..9. This can be easily tested by attempting to run Frama-C on single-line files containing each of the above examples.

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