From: | Victor Wagner <vitus(at)wagner(dot)pp(dot)ru> |
---|---|
To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: master make check fails on Solaris 10 |
Date: | 2018-01-18 15:05:12 |
Message-ID: | 20180118180512.066098de@fafnir.local.vm |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, 18 Jan 2018 09:56:48 -0500
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Marina Polyakova <m(dot)polyakova(at)postgrespro(dot)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.
--
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-01-18 15:19:43 | Re: master make check fails on Solaris 10 |
Previous Message | David Rowley | 2018-01-18 15:03:26 | Re: [Sender Address Forgery]Re: [Sender Address Forgery]Re: [Sender Address Forgery]Re: [HACKERS] path toward faster partition pruning |