| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Greg Stark <stark(at)mit(dot)edu>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: longjmp clobber warnings are utterly broken in modern gcc |
| Date: | 2015-01-26 11:09:31 |
| Message-ID: | 20150126110931.GC9916@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2015-01-25 15:40:10 -0500, Tom Lane wrote:
> Greg Stark <stark(at)mit(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marko Tiikkaja | 2015-01-26 12:02:05 | Re: PL/pgSQL, RAISE and error context |
| Previous Message | Andres Freund | 2015-01-26 11:03:17 | Re: longjmp clobber warnings are utterly broken in modern gcc |