Re: LLVM breakage on seawasp
| От | Tom Lane |
|---|---|
| Тема | Re: LLVM breakage on seawasp |
| Дата | |
| Msg-id | 343.1566682675@sss.pgh.pa.us обсуждение |
| Ответ на | Re: LLVM breakage on seawasp (Andres Freund <andres@anarazel.de>) |
| Ответы |
Re: LLVM breakage on seawasp
|
| Список | pgsql-hackers |
Andres Freund <andres@anarazel.de> writes:
> On August 24, 2019 1:57:56 PM PDT, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> So we're depending on APIs that upstream doesn't think are stable?
> Seawasp iirc builds against the development branch of llvm, which explains why we see failures there. Does that
addresswhat you are concerned about? If not, could you expand?
I know it's the development branch. The question is whether this
breakage is something *they* ought to be fixing. If not, I'm
worried that we're too much in bed with implementation details
of LLVM that we shouldn't be depending on.
regards, tom lane
В списке pgsql-hackers по дате отправления: