Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 334726 - Constructs should be allowed when using STATIC_POLICY
Summary: Constructs should be allowed when using STATIC_POLICY
Status: CLOSED DUPLICATE of bug 349505
Alias: None
Product: RTSC
Classification: Technology
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Dave Russo CLA
QA Contact:
URL:
Whiteboard: target:3.23
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-18 21:02 EST by Scott Gary CLA
Modified: 2011-11-04 21:26 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Scott Gary CLA 2011-01-18 21:02:37 EST
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).
Comment 1 Dave Russo CLA 2011-08-01 10:45:24 EDT
marking this as a duplicate of 349505 (since it has now more comments)

*** This bug has been marked as a duplicate of bug 349505 ***