Re: LLVM breakage on seawasp

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: LLVM breakage on seawasp
Date: 2019-08-24 21:15:35
Message-ID: CA+hUKGJ_1a4V03BnRadb24d+iVD0HKKePdA5AWky_jhJnNSAqA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Aug 25, 2019 at 8:24 AM Andres Freund <andres(at)anarazel(dot)de> wrote:
> On August 24, 2019 1:08:11 PM PDT, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> >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.
>
> Perhaps just a
> #if new_enough
> using std::make_unique
> #else
> using llvm::mak_eunique
>
> At the start of the file, and then use it unqualified?

Yeah, it's a pain though, you'd have to say:

#if llvm >= 9
# if cpp >= 14
# using std::make_unique;
# else
# error "postgres needs at least c++ 14 to use llvm 9"
# endif
#else
# using llvm::make_unique;
#endif

Maybe we should just use std::unique_ptr's constructor, ie give it new
ImportMayTy() instead of using make_unique(), even though that's not
cool C++ these days?

--
Thomas Munro
https://enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-08-24 21:37:55 Re: LLVM breakage on seawasp
Previous Message Andres Freund 2019-08-24 21:11:00 Re: LLVM breakage on seawasp