On Thu, 18 Jan 2018 09:56:48 -0500 Tom Lane <t...@sss.pgh.pa.us> wrote:
> Marina Polyakova <m.polyak...@postgrespro.ru> writes: > > Applying your patch on commit > > f033462d8f77c40b7d6b33c5116e50118fb4699d and using the > > configuration command from [1], I got: checking for __int128... yes > > checking for __int128 alignment bug... broken > > ... > > And make check-world passes. Victor said that he used a much > > simpler configuration command, and I'm trying to figure out what's > > changed.. > > Weird. Maybe the gcc bug only manifests with certain optimization > flags? That's not what I'd have expected from Victor's theory about No. I've compiled test program without any optimizationf flags. Just -m64, which tells compiler to generate 64-bit code. (in 32-bit mode there is no __int128, so problem wouldn't manifest inself). From the other side, when I've tried to resolve issue with not worked test, I've copied all gcc flags from config.log, and test program returned 1 with exactly same flags. Probably, I should have to regenerate configure with autoconf. instead of applying patch to configure. --
