Constraints killed by Globals.
| Bugzilla Link | 393 |
| Created on | Aug 23, 2007 20:37 |
| Resolution | FIXED |
| Resolved on | Aug 24, 2007 16:43 |
| Version | 1.00beta |
| OS | Linux |
| Architecture | PC |
Extended Description
Kai says: "I committed code that allows to compile the stdlib with -ecc -dosaa -check c. It takes ages and the tree grows to unbelievable sizes, but I guess this is what we wanted. However, when compiling classes/random/Rand.sac, a global object appears in an afterguard. This then kills MMV. Since I have no idea how global objects should be handled wrt constraint checks, I would like someone else to have a look at it." I just reproduced this with build #15582. The fault is in MMVprfAfterGuard, buried in one of the macros in the line that invokes the first LUT insertion.As Kai points out, there is a global object in "a": Rand48::RandomGen.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information