On Wed, 2020-01-08 at 04:02 -0500, David Malcolm wrote: > Jeff reviewed an earlier version of this here: > https://gcc.gnu.org/ml/gcc-patches/2019-12/msg00503.html > My response: > https://gcc.gnu.org/ml/gcc-patches/2019-12/msg00809.html > I have followup patches that implement the function_set idea. > > TODO: > I haven't yet addressed the is_setjmp_call_p/is_longjmp_call_p concerns > > Changed in v5: > - update ChangeLog path > - updated copyright years to include 2020 > > Changed in v4: > - Remove include of gcc-plugin.h, reworking includes accordingly. > - Wrap everything in #if ENABLE_ANALYZER > - Remove /// comment lines > - Update is_named_call_p to support function pointers: > https://gcc.gnu.org/ml/gcc-patches/2019-12/msg00178.html > > gcc/analyzer/ChangeLog: > * analyzer.cc: New file. > * analyzer.h: New file. So there's a lot more ways to write setjmp. Some don't even look like setjmp. sigsetjmp, savectx, vfork, getcontext all have setjmp like qualities (returning twice). They may have an underscore prefix IIRC.
So if what you're really looking for is functions that may return twice, I think that's the canonical list :-) jeff
