Re: BUG #15270: __builtin_isinf conflict when building using clang

From: Andres Freund <andres(at)anarazel(dot)de>
To: steven(dot)winfield(at)cantabcapital(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15270: __builtin_isinf conflict when building using clang
Date: 2018-09-01 00:12:00
Message-ID: 20180901001200.35wf3uz2u6jlsosr@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2018-07-09 19:00:31 +0000, PG Bug reporting form wrote:
> The following bug has been logged on the website:
>
> Bug reference: 15270
> Logged by: Steven Winfield
> Email address: steven(dot)winfield(at)cantabcapital(dot)com
> PostgreSQL version: 11beta2
> Operating system: RHEL 7.4
> Description:
>
> Hi,
>
> I've been experimenting with getting the whole of PG 11beta2 (not just the
> JIT) compiling with the most recent stable version of llvm/clang: 6.0.1.
>
> TL;DR: In src/include/port.h, inside the #else branch of #ifndef HAVE_ISINF,
> there probably need to be some glibc version checks within the #ifdef
> __clang__ block.

The actual problem appears to be issues within libc++ (rather than
libstdc++). I nevertheless have restricted it to C for now, as there's
no performance issue with the tiny amount of C++ in postgres.

We probably need to find a better solution.

Sorry for the late response!

Greetings,

Andres Freund

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2018-09-01 06:58:24 BUG #15360: Cascade slave cannot continue replication without manual restart after master server crash/restart.
Previous Message jhm713 2018-08-31 19:22:58 Re: Inconsistencies restoring public schema ownership from pg_dump