Opened 11 years ago
Last modified 7 years ago
#2335 new enhancement
Look into pattern-matching efficiency
Reported by: | Martin Sjölund | Owned by: | Martin Sjölund |
---|---|---|---|
Priority: | high | Milestone: | Future |
Component: | Code Generation | Version: | trunk |
Keywords: | Cc: |
Description (last modified by )
Currently, matchcontinue generates code like:
CevalScript_createSimulationResultFailure_rettype tmp161; if (8 != MMC_STRLEN(tmpMeta[3+2]) || strcmp("simulate", MMC_STRINGDATA(tmpMeta[3+2])) != 0) MMC_THROW(); if (listEmpty(tmpMeta[3+3])) MMC_THROW(); tmpMeta[503] = MMC_CAR(tmpMeta[3+3]); tmpMeta[504] = MMC_CDR(tmpMeta[3+3]); if (mmc__uniontype__metarecord__typedef__equal(tmpMeta[503],12,1) == 0) MMC_THROW();
It should be possible to make this call continue
instead of MMC_THROW()
Change History (7)
comment:1 by , 11 years ago
Description: | modified (diff) |
---|
comment:2 by , 9 years ago
Milestone: | 1.9.3 → 1.9.4 |
---|
comment:6 by , 8 years ago
Milestone: | 1.11.0 → 1.12.0 |
---|
Milestone moved to 1.12.0 due to 1.11.0 already being released.
comment:7 by , 7 years ago
Milestone: | 1.12.0 → Future |
---|
The milestone of this ticket has been reassigned to "Future".
If you think the issue is still valid and relevant for you, please select milestone 1.13.0 for back-end, code generation and run-time issues, or 2.0.0 for front-end issues.
If you are aware that the problem is no longer present, please select the milestone corresponding to the version of OMC you used to check that, and set the status to "worksforme".
In both cases, a short informative comment would be welcome.
Moved to new milestone 1.9.4