Timeline for Multithreaded Pre/Post Functions
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 2, 2014 at 6:05 | vote | accept | clambake | ||
| Sep 1, 2014 at 19:48 | answer | added | Radian | timeline score: 1 | |
| Sep 1, 2014 at 18:27 | comment | added | Radian | I have a couple ideas, but it's easier to make suggestions if we can move this discussion from the abstract ("an RTOS") to the concrete (e.g. "we're using Micrium's uC/OS-II" or whatever). Would it be possible for you to name the RTOS? | |
| Aug 28, 2014 at 14:34 | comment | added | david.pfx | Surely if START/END are held as local variables on the call stack they will be immune to threading issues? | |
| Aug 28, 2014 at 14:33 | comment | added | david.pfx | TLS has been around as long as threads, at least 20 years. Your compiler probably has a way, if you talk to it nicely. | |
| Aug 28, 2014 at 14:00 | history | tweeted | twitter.com/#!/StackProgrammer/status/504991903717556224 | ||
| Aug 28, 2014 at 11:37 | comment | added | clambake | it's a seperate stack | |
| Aug 28, 2014 at 11:34 | comment | added | Bart van Ingen Schenau | Are the START/END numbers stored on the function call stack (the one that also holds the parameters & return addresses) or in a separate data structure with stack semantics? | |
| Aug 28, 2014 at 9:34 | comment | added | clambake | EDIT: It does not support C++11 but seems to support TLS. I'm having a deeper look. | |
| Aug 28, 2014 at 9:33 | comment | added | clambake | great idea, unfortunately our compiler does not support C++11 :( | |
| Aug 28, 2014 at 8:49 | comment | added | ratchet freak | hint: thread local storage | |
| Aug 28, 2014 at 8:47 | history | asked | clambake | CC BY-SA 3.0 |