Opened 13 years ago
Closed 4 years ago
#1597 closed defect (fixed)
Remove DAE.MATRIX
| Reported by: | Martin Sjölund | Owned by: | Martin Sjölund |
|---|---|---|---|
| Priority: | high | Milestone: | Future |
| Component: | New Instantiation | Version: | |
| Keywords: | Cc: | Martin Sjölund |
Description
To have a special case for 2d-arrays seems a bit silly. It's easier to just focus on generating efficient code from nested array-constructors (and then maybe get good code for 3d-arrays). DAE.MATRIX does not really fill any purpose other than making the compiler more complicated than it should be.
To start off the refactoring this would require, start by changing from list<list<tuple<Exp,Boolean>> to list<list<Exp>>,Boolean
Change History (4)
comment:1 by , 13 years ago
comment:2 by , 13 years ago
More work than I expected (so this will be on my forever growing stack). The problem is that expression simplification currently does special tricks with matrix operations as they are different from array-ops.
comment:3 by , 9 years ago
| Cc: | sjoelund.se, → sjoelund.se |
|---|---|
| Milestone: | → Future |
comment:4 by , 4 years ago
| Component: | → New Instantiation |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
The new frontend converts matrices to arrays during type checking, so it does not generate any DAE.MATRIX.
Added a new field Boolean scalar to DAE.MATRIX instead of the old structure