Re: longjmp clobber warnings are utterly broken in modern gcc

From: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
To: Martijn van Oosterhout <kleptog(at)svana(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: longjmp clobber warnings are utterly broken in modern gcc
Date: 2015-02-01 17:48:50
Message-ID: 54CE6702.3070503@vmware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2015-02-01 17:50:28 Re: Re: [COMMITTERS] pgsql: Another attempt at fixing Windows Norwegian locale.
Previous Message Heikki Linnakangas 2015-02-01 17:45:39 Re: Re: [COMMITTERS] pgsql: Another attempt at fixing Windows Norwegian locale.