From: | "Tharakan, Robins" <tharar(at)amazon(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Rowley <dgrowleyml(at)gmail(dot)com> |
Cc: | "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | RE: Why is parula failing? |
Date: | 2024-04-02 02:06:14 |
Message-ID: | a1e56c889422463ebb0a7e4de0b8f596@amazon.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> ... in connection with which, I can't help noticing that parula is using a very old compiler:
>
> configure: using compiler=gcc (GCC) 7.3.1 20180712 (Red Hat 7.3.1-17)
>
> From some quick checking around, that would have to be near the beginning of aarch64
> support in RHEL (Fedora hadn't promoted aarch64 to a primary architecture until earlier
> that same year). It's not exactly hard to believe that there were some lingering compiler bugs.
> I wonder why parula is using that when its underlying system seems markedly newer (the kernel at least has a recent build date).
Parula used GCC v7.3.1 since that's what came by default.
I've now switched to GCC v13.2 and triggered a run. Let's see if the tests stabilize now.
-
Robins
From | Date | Subject | |
---|---|---|---|
Next Message | Andrei Lepikhov | 2024-04-02 03:07:35 | Re: Asymmetric partition-wise JOIN |
Previous Message | Japin Li | 2024-04-02 00:57:47 | Re: Table AM Interface Enhancements |