> "In practice, this is usually handled by not attempting to optimise > routines that include a call to setjmp(), but putting in phantom > control-flow edges is a (usually very pessimistic) alternative."
There are some optimizations that can't be made when you use setjmp, but they're minor. Assume gcc knows all about setjmp. However, if you're using setjmp where a simple "break" or "return" will do, you're probably better off not using setjmp. It's better for deep returns, especially when you're searching for something and you need to escape the whole search. Note that setjmp/longjmp themselves are more expensive than simple returns, also. _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
