| Summary: | Constructs should be allowed when using STATIC_POLICY | ||
|---|---|---|---|
| Product: | [Technology] RTSC | Reporter: | Scott Gary <sg> |
| Component: | Core | Assignee: | Dave Russo <d-russo> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | target:3.23 | ||
marking this as a duplicate of 349505 (since it has now more comments) *** This bug has been marked as a duplicate of bug 349505 *** |
Build Identifier: xdctools_3_21_00_23 Presently, constructs are not permitted when a static policy is selected. For example, with: var Defaults = xdc.useModule('xdc.runtime.Defaults'); Defaults.common$.memoryPolicy = xdc.module('xdc.runtime.Types').STATIC_POLICY; a runtime an error is thrown if a construct is attempted, for example: ti.sysbios.knl.Semaphore: create policy error xdc.runtime.Error.raise: terminating execution Since constructs use stack space, they should *not* be prohibited when using a static policy. Reproducible: Always Steps to Reproduce: 1.Select STATIC_POLICY 2.Attempt a construct, either directly, or via an API call that uses a construct (e.g., via SYS/BIOS' Task_sleep(), that does an internal construct).