Re: longjmp clobber warnings are utterly broken in modern gcc

On 02/01/2015 03:56 PM, Martijn van Oosterhout wrote:
> If you want the compiler to catch this, I don't see any way without
> requiring the code to indicate specifically which local variables it
> intends to use, or not using the locals at all by using a seperate
> cleanup function (as discussed elsewhere in this thread).  With
> information about the locals you might be able to conjure some GCC
> macros to set things up to complain if you use anything else.

I wonder how difficult it would be to teach e.g. clang static analyzer 
to catch this, rather than the compiler.

- Heikki