Re: Raising our compiler requirements for 9.6

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Noah Misch <noah(at)leadboat(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Raising our compiler requirements for 9.6
Date: 2015-08-05 14:29:12
Message-ID: 20150805142912.GH12598@awork2.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2015-08-05 10:23:31 -0400, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
> > How about moving that error check into into the aix template file and
> > erroring out there? Since this is master I think it's perfectly fine to
> > refuse to work with the buggy unsupported 32 bit compiler. The argument
> > not to do so was that PG previously worked in the back branches
> > depending on the minor version, but that's not an argument on master.
>
> The check as Noah wrote it rejects *all* 32-bit IBM compilers, not just
> buggy ones. That was okay when the effect was only a rather minor
> performance loss, but refusing to build at all would raise the stakes
> quite a lot. Unless you are volunteering to find out how to tell broken
> compilers from fixed ones more accurately, I think you need to confine
> the effects of the check to disabling inlining.

Wasn't the point that 32 bit AIX as a whole hasn't been supported for a
couple years now? My willingness to expend effort for that is rather
limited.

I mean I'd otherwise ok with a PG_FORCE_DISABLE_INLINE flag that takes
effect in c.h or so. That could easily be set in src/template/aix. Might
also be useful for investigatory purposes every couple years or so.

Andres

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2015-08-05 14:32:48 Re: Raising our compiler requirements for 9.6
Previous Message Tom Lane 2015-08-05 14:23:31 Re: Raising our compiler requirements for 9.6