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
  • #2061

Cil problem about scope in initialization ?

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


Id Project Category View Due Date Updated
ID0001143 Frama-C Kernel public 2012-04-06 2012-04-06
Reporter Anne Assigned To virgile Resolution no change required
Priority normal Severity minor Reproducibility have not tried
Platform - OS - OS Version -
Product Version - Target Version - Fixed in Version -

Description :

This is about hiding a variable by redefining another one with the same name, and using the first one in the initialization of the second one.

This is a stupid example : int main (void) { int x = 0; int y; { int x = x+1; y = x; } return y; }

$ frama-c -print toto.c

int main(void) { int x; int y; x = 0; { int x_0; x_0 ++; y = x_0; } return (y); }

Shouldn't we have: x_0 = x + 1; instead of x_0 ++; ??? It seems that gcc agrees with me...

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