Re: longjmp clobber warnings are utterly broken in modern gcc - Mailing list pgsql-hackers

From Andres Freund
Subject Re: longjmp clobber warnings are utterly broken in modern gcc
Date
Msg-id 20150126110931.GC9916@awork2.anarazel.de
Whole thread Raw
In response to Re: longjmp clobber warnings are utterly broken in modern gcc  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 2015-01-25 15:40:10 -0500, Tom Lane wrote:
> Greg Stark <stark@mit.edu> writes:
> > Perhaps Clang has a more useful warning?
> 
> Clang, at least the version on my Mac, doesn't warn either with the
> settings we normally use, and it doesn't have -Wclobber at all.
> I tried turning on -Weverything, and it still didn't complain.
> (It did generate incorrect code though, so it's no better than gcc
> in that respect.)

Even a pretty recent (3.6-rc1) clang doesn't warn. It generates lots of
useful warnings, but nothing about longjmp clobbers.

Greetings,

Andres Freund

-- Andres Freund                       http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: longjmp clobber warnings are utterly broken in modern gcc
Next
From: Marko Tiikkaja
Date:
Subject: Re: PL/pgSQL, RAISE and error context