Andres Freund <and...@anarazel.de> writes: > On 2023-04-14 13:21:33 -0400, Tom Lane wrote: >> ... I'm not sure why only those two animals >> are unhappy, but I think they have a point: typical ABIs don't >> guarantee alignment of function stack frames to better than >> 16 bytes or so. In principle the compiler could support a 4K >> alignment request anyway by doing the equivalent of alloca(3), >> but I do not think we can count on that to happen.
> Hm. New-ish compilers seem to be ok with it. Oh! I was misled by the buildfarm label on morepork, which claims it's running clang 10.0.1. But actually, per its configure report, it's running configure: using compiler=gcc (GCC) 4.2.1 20070719 which is the same as curculio. So that explains why nothing else is complaining. I agree we needn't let 15-year-old compilers force us into the mess that would be entailed by not treating these variables as simple locals. > Perhaps we should have a > configure check whether the compiler is OK with that, and disable direct IO > support if not? +1 for that, though. (Also, the fact that these animals aren't actually failing suggests that 004_io_direct.pl needs expansion.) regards, tom lane