Timeline for Loop without 'looping'
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 11, 2014 at 7:01 | comment | added | PTwr | @BrianMinton My guess is because it is in CPU specs, which makes it (hardware) platform dependent. And it is rather dangerous to use when stackframe is auto-generated, I would not be surprised if AV would cry about such code. Check this or this for x86 asm versions. | |
| Jul 9, 2014 at 21:00 | history | edited | Digital Trauma | CC BY-SA 3.0 |
added 1 character in body
|
| Jul 9, 2014 at 20:35 | comment | added | Digital Trauma |
@BrianMinton Actually a similar thing should be achievable with setjmp()/longjmp(). These aren't in the c standard, but are in the standard library. I felt like munging the stack manually today though ;-)
|
|
| Jul 9, 2014 at 20:16 | comment | added | Brian Minton | nice! I wonder why those functions aren't part of the C spec? ;-D | |
| Jul 9, 2014 at 17:55 | history | edited | Digital Trauma | CC BY-SA 3.0 |
added 111 characters in body
|
| Jul 9, 2014 at 17:41 | history | edited | Digital Trauma | CC BY-SA 3.0 |
added 23 characters in body
|
| Jul 9, 2014 at 17:32 | history | edited | Digital Trauma | CC BY-SA 3.0 |
deleted 283 characters in body
|
| Jul 9, 2014 at 17:18 | history | edited | Digital Trauma | CC BY-SA 3.0 |
added 738 characters in body
|
| Jul 9, 2014 at 17:11 | history | answered | Digital Trauma | CC BY-SA 3.0 |