![[logo]](/img/veripool_small.png)
Issue #247
commit ed17581f92c introduces new UNOPTFLAT warnings
| Status: | Closed | Start date: | 04/19/2010 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | Wilson Snyder | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - |
Description
We have a couple of blocks that no longer build with the latest code from git. A git-bisect blamed commit ed17581f92ce5cb92570d1191f7ca1ecc2a24831 and the warnings go away if I revert that commit. I'm assuming this is a bug and it's not just detecting problems that it wasn't before. Let me know if I can provide any more information.
History
Updated by Wilson Snyder about 2 years ago
- Status changed from New to AskedReporter
- Assignee set to Wilson Snyder
The interpretation of --unroll-stmts changed, so probably it's just not unrolling something it used to. If you find the right value for unroll stmts that makes it work, I'll bump up the default.
Updated by Byron Bradley about 2 years ago
Thanks Wilson, all of our code builds again with --unroll-stmts 21800
Updated by Wilson Snyder about 2 years ago
- Status changed from AskedReporter to Closed
Upped it to 30000 as the default.
Also available in: Atom