On Monday 27 July 2009 18:27:17 Mark wrote:
> One particular gotcha in setjmp is when the stack is too modified
> at resume; for instance when resuming after a function is already
> complete; without seeing the actual code that is upsetting you,
> I'd say it would be possible that compiler optimization makes the
> difference between the cases
It isn't even certain that setjmp is involved at all. The OP seems
to have jumped to a conclusion that the switch from SJLJ exception
handling to the Dwarf-2 model is somehow responsible, but that
clearly isn't the case, because there is no exception handler in
play; (the code is C, and the EH model is exclusive to C++).
Since we haven't been shown any code, or even any diagnostics, we
really can't offer anything but sheer speculation anyway.
--
Regards,
Keith.
------------------------------------------------------------------------------
_______________________________________________
MinGW-users mailing list
MinGW-users@...
This list observes the Etiquette found at
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same.
Most annoying abuses are:
1) Top posting
2) Thread hijacking
3) HTML/MIME encoded mail
4) Improper quoting
5) Improper trimming
_______________________________________________
You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users
