#3710 closed defect (invalid)
Unlucky tearing if module wrapFucntionCalls is enabled
| Reported by: | Lennart Ochel | Owned by: | somebody |
|---|---|---|---|
| Priority: | high | Milestone: | Future |
| Component: | Optimization | Version: | v1.9.4-dev-nightly |
| Keywords: | Cc: | jan.hagemann@…, Patrick Täuber |
Description
The two tests testAlgLoop5.mos and testAlgLoop6.mos fail if post-optimization module wrapFunctionCalls is enabled. The problem seem to be connected to input variables.
Change History (5)
follow-up: 2 comment:1 by , 9 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
| Summary: | Some optimization tests does not work if module wrapFucntionCalls is enabled → Unlucky tearing if module wrapFucntionCalls is enabled |
comment:2 by , 9 years ago
| Cc: | added |
|---|
Replying to vitalij:
wrapFunctionCalls changes unlucky the tearing set.
Can you explain this a bit? Do you think this is a tearing issue?
follow-up: 4 comment:3 by , 7 years ago
| Resolution: | → invalid |
|---|---|
| Status: | assigned → closed |
These tests use a flag that enables a careless tearing (--tearingStrictness=casual). Use --tearingStrictness=casualto avoid problems.
follow-up: 5 comment:4 by , 7 years ago
Replying to ptaeuber:
These tests use a flag that enables a careless tearing (
--tearingStrictness=casual). Use--tearingStrictness=casualto avoid problems.
@ptauber you wrote '--tearingStrictness=casual' twice. What is the right flag to use?
comment:5 by , 7 years ago
Replying to casella:
@ptauber you wrote '--tearingStrictness=casual' twice. What is the right flag to use?
Oops, it has to be --tearingStrictness=strict, which is the default.
wrapFunctionCalls changes unlucky the tearing set.