What portable ways exist to change the stack frame to an arbitrary buffer? Say to:
char stack[1024];
or
new char[1024];
Asked
Active
Viewed 87 times
0
-
11There are no portable ways to do this. – Sam Varshavchik Oct 13 '16 at 23:07
-
I'd recommend a `std::stack` and loops or such. – πάντα ῥεῖ Oct 13 '16 at 23:09
-
4It's a common misconception that C standardises anything about the "stack" and the "heap". – Oct 13 '16 at 23:13
-
1^^^^ Same for C++. – Baum mit Augen Oct 13 '16 at 23:14
-
`va_start, va_arg` won't work. – Adrian Colomitchi Oct 13 '16 at 23:22
-
@BaummitAugen: Of course C++ does. It standardizes `make_heap`, `push_heap`, `pop_heap` etc. :-) – Jerry Coffin Oct 13 '16 at 23:23
-
http://stackoverflow.com/q/17768925/315052 – jxh Oct 13 '16 at 23:27
-
The least un-portable way is to use `std::longjmp`. But it's not guaranteed to save all state you're interested in. So it would probably have to be supported by some assembly code (that was the case when I used it for some co-routine like stuff in the 1990s), and then for portability you'd be worse off for having added the dependency on that function. By the way, just ignore the terminology comments. They're not constructive, they essentially just say that those making those comments, lack a reasonably good understanding of things. – Cheers and hth. - Alf Oct 13 '16 at 23:31
-
I meant, least un-portable using only the standard library. I'd forgotten about Boost.Context, pointed by Travis Gockel in his answer below. Sorry. – Cheers and hth. - Alf Oct 13 '16 at 23:51
1 Answers
1
I believe what you are looking for is Boost.Context. To switch the current running context (what you are calling a "stack") to an arbitrary buffer, use boost::context::preallocated when creating your boost::context::context<T> instance.
Travis Gockel
- 26,877
- 14
- 89
- 116