From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>, Christoph Berg <myon(at)debian(dot)org>, mikael(dot)kjellstrom(at)gmail(dot)com, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Direct I/O |
Date: | 2023-04-15 22:10:59 |
Message-ID: | 2068346.1681596659@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> Full GCC support including stack objects actually began in 4.6, it
> seems.
Hmm. The oldest gcc versions remaining in the buildfarm seem to be
curculio | configure: using compiler=gcc (GCC) 4.2.1 20070719
frogfish | configure: using compiler=gcc (Debian 4.6.3-14) 4.6.3
lapwing | configure: using compiler=gcc (Debian 4.7.2-5) 4.7.2
skate | configure: using compiler=gcc-4.7 (Debian 4.7.2-5) 4.7.2
snapper | configure: using compiler=gcc-4.7 (Debian 4.7.2-5) 4.7.2
buri | configure: using compiler=gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44)
chub | configure: using compiler=gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44)
dhole | configure: using compiler=gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44)
mantid | configure: using compiler=gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44)
prion | configure: using compiler=gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-28)
rhinoceros | configure: using compiler=gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44)
siskin | configure: using compiler=gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44)
shelduck | configure: using compiler=gcc (SUSE Linux) 4.8.5
topminnow | configure: using compiler=gcc (Debian 4.9.2-10+deb8u1) 4.9.2
so curculio should be the only one that's at risk here.
Maybe just upgrading it is the right answer.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Pryzby | 2023-04-15 22:20:50 | Re: Direct I/O |
Previous Message | Thomas Munro | 2023-04-15 21:48:58 | Re: Direct I/O |