Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • sac2c sac2c
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 336
    • Issues 336
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Infrastructure Registry
  • External wiki
    • External wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • sac-group
  • sac2csac2c
  • Issues
  • #1163

Closed
Open
Created Mar 08, 2014 by Robert Bernecky@rbeDeveloper

Revealed guards do not rename dominated successors

Bugzilla Link 1119
Created on Mar 08, 2014 21:00
Version svn
OS Linux
Architecture PC

Extended Description

I think this problem has been around forever, but it is certainly with us
as of:
sac2c v1.00-beta (Haggis And Apple)
 developer rev 18449 linux-gnu_x86_64
 (Sat Mar  8 13:24:26 EST 2014 by sac)
In ~/sac/testsuite/optimizations/constraintchecks/ipbb.sac,
we have something like:
   x = condfun(... colx);
   ...
   colx' = val_le_SxS_( 0, colx);
Eventually, condfun gets inlined, and with it comes a guard:
   colx2 = _non_neg_val( colx);
   x = blah;
   ...
   colx' = val_le_SxS_( 0, colx);
The latter guard can not be removed. However, since the guard
on colx dominates the second guard, we could arrange to rename
colx --> colx2, in all code dominated by the first guard,
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking