Opened 14 years ago
Closed 12 years ago
#1327 closed task (fixed)
Use DAE.Type instead of DAE.ExpType everywhere
| Reported by: | Adrian Pop | Owned by: | Adrian Pop |
|---|---|---|---|
| Priority: | low | Milestone: | |
| Component: | Backend | Version: | |
| Keywords: | Cc: | Adrian Pop, Per Östlund |
Description
Right now we have two types: DAE.Type which we translate to DAE.ExpType.
We should *REMOVE* DAE.ExpType as the DAE.Type -> DAE.ExpType translation
consumes a lot of CPU and Memory for nothing.
Change History (3)
comment:1 by , 14 years ago
comment:2 by , 14 years ago
We decided this should not be part of White December as the type memory works rather well for now.
comment:3 by , 12 years ago
| Cc: | adrpo, adrpo, perost → adrpo, perost |
|---|---|
| Component: | → Backend |
| Resolution: | → fixed |
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
The conversion
DAE.Type->DAE.ExpTypeand storage of both thesetypes in env and every cref is a memory/CPU killer.
A model by Pavol Privitzer fails to flatten (as it would require 30GB of memory)
currently (trunk revision 6492), but flattens fine using ONLY 480MB if
DAE.ExpTypefrom crefs are shared (only one unique exp type in the memory).
Conclusion: We SHOULD REALLY GET RID OF
DAE.ExpTypeand maybe shareDAE.Type.