Re: LLVM breakage on seawasp - Mailing list pgsql-hackers

From Tom Lane
Subject Re: LLVM breakage on seawasp
Date
Msg-id 27807.1566680276@sss.pgh.pa.us
Whole thread Raw
In response to Re: LLVM breakage on seawasp  (Andres Freund <andres@anarazel.de>)
Responses Re: LLVM breakage on seawasp  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
Andres Freund <andres@anarazel.de> writes:
> On August 24, 2019 1:08:11 PM PDT, Thomas Munro <thomas.munro@gmail.com> wrote:
>> That's because they just moved to C++14 and replaced their own
>> llvm::make_unique<> with std::make_unique<>:
>> https://github.com/llvm-mirror/llvm/commit/114087caa6f95b526861c3af94b3093d9444c57b
>> Perhaps we'll need some macrology to select between llvm and std
>> versions?  I am guessing we can't decree that PostgreSQL's minimum C++
>> level is C++14 and simply change it to std::make_unique.

So we're depending on APIs that upstream doesn't think are stable?

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: assertion at postmaster start
Next
From: Andres Freund
Date:
Subject: Re: LLVM breakage on seawasp