https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40115
--- Comment #6 from Per Lundberg <perlun at gmail dot com> --- Well, the label is actually in the same function. It just happens to land there on the other thread. I can't really use a function pointer here, since I have no way (at least that I know of) to find out how much the stack pointer is offset within the function. In fact, I tried that approach but it failed specifically because of that (when trying to return from the other function, since esp wasn't pointing at the right adress). I am using -fomit-frame-pointers, otherwise I guess I could just take the ebp value. Any other suggestion? — Sent from Mailbox On Wed, May 6, 2015 at 11:52 PM, pinskia at gcc dot gnu.org <gcc-bugzi...@gcc.gnu.org> wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40115 > --- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> --- >> In my case, I use the address for "jumping" but with indirect jumping >> (in the new thread being created). Would you say that this is not supported? > yes that is not support is explicitly says it is not support: "You may not use > this mechanism to jump to code in a different function. ". You just caused a > jump to a different function. For these kind of things you should be using > functions and function pointers instead of label addresses. > -- > You are receiving this mail because: > You are on the CC list for the bug.
