- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi friends,
With CVF, we had a routine that declared a large array (say 50mb). Since we did not adjust the CVF program stack size, I think I can assume that the CVF compiler chose to put this on the heap instead of the stack.
With our current project settings, IVF tries to put this on the stack, and we need 64mb of stack for the routine to not crash on entry. Is there a way to trick or force IVF to put large variables on the heap, perhaps with some AUTOMATIC setting, or reentrency or SAVE or something.
Regards,
- Jeremy
With CVF, we had a routine that declared a large array (say 50mb). Since we did not adjust the CVF program stack size, I think I can assume that the CVF compiler chose to put this on the heap instead of the stack.
With our current project settings, IVF tries to put this on the stack, and we need 64mb of stack for the routine to not crash on entry. Is there a way to trick or force IVF to put large variables on the heap, perhaps with some AUTOMATIC setting, or reentrency or SAVE or something.
Regards,
- Jeremy
Link Copied
3 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Read about the
/heap-arrays[:n]
compiler option.
/heap-arrays[:n]
compiler option.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
CVF made the array static, not on the heap.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Both excellent answers and very helpful.
Thanks - Jeremy
Thanks - Jeremy
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page