pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Marina Polyakova <m.polyakova@postgrespro.ru>
Cc: vitus@wagner.pp.ru, Andres Freund <andres@anarazel.de>
Cc: pgsql-hackers@postgresql.org, Alvaro Herrera <alvherre@alvh.no-ip.org>
Subject: Re: master make check fails on Solaris 10
Date: Thu, 18 Jan 2018 11:53:01 -0500
Message-ID: <5487.1516294381@sss.pgh.pa.us> (raw)
In-Reply-To: <c737e36bb5eee1fa1c0f24dc33ba9e2e@postgrespro.ru>
References: <0d3a9fa264cebe1cb9966f37b7c06e86@postgrespro.ru>
	<20180111173938.jimybeayp2u5mmup@alap3.anarazel.de>
	<31a342fa6a025a8bdfc5b8b19c29d56d@postgrespro.ru>
	<fc3c1b52d2d4121cccfc13635005bbd0@postgrespro.ru>
	<1232.1515780057@sss.pgh.pa.us>
	<b946893927ccfd87146d8a7c9f3bbe29@postgrespro.ru>
	<15299.1515867055@sss.pgh.pa.us>
	<a5559105243efcf6fb619d86c5702115@postgrespro.ru>
	<18209.1516059711@sss.pgh.pa.us>
	<90ab676392c8f9c84431976147097cf0@postgrespro.ru>
	<17897.1516202926@sss.pgh.pa.us>
	<1c70bab595a37ffa3a7fafea29fa6f55@postgrespro.ru>
	<31743.1516206789@sss.pgh.pa.us>
	<0e183c12a68af526ebc03c5c26206c44@postgrespro.ru>
	<16822.1516287408@sss.pgh.pa.us>
	<c737e36bb5eee1fa1c0f24dc33ba9e2e@postgrespro.ru>

Marina Polyakova <m.polyakova@postgrespro.ru> writes:
> On 18-01-2018 17:56, Tom Lane wrote:
>> Weird.  Maybe the gcc bug only manifests with certain optimization
>> flags?  That's not what I'd have expected from Victor's theory about
>> why the code is wrong, but if it only shows up some of the time,
>> it's hard to think of another explanation.

> Thank you! Using ./configure CC="gcc" CFLAGS="-m64 -O1" on commit 
> 9c7d06d60680 with your patch, I got this:
> [ configure check passes ]
> But make check got the same failures, and I see the same debug output as 
> in [1]..

Interesting.  Maybe the parameter-passing misbehavior that Victor's
test is looking for isn't the only associated bug.

> P.S. As I understand it, this comment on bugzilla [2] is also about 
> this.
> [2] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83925#c6

Even more interesting, see c7 that was just posted there:

>> Eric Botcazou 2018-01-18 16:22:48 UTC
>> 128-bit types requite 128-bit alignment on SPARC64 so we cannot support that.

So basically, we're outta luck and we have to consider __int128 as
unsupportable on SPARC.  I'm inclined to mechanize that as a test on
$host_cpu.  At least that means we don't need an AC_RUN test ;-)

			regards, tom lane




view thread (46+ messages)  latest in thread

Message-ID: <5487.1516294381@sss.pgh.pa.us>
Permalink:  ../5487.1516294381@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/5487.1516294381@sss.pgh.pa.us

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, m.polyakova@postgrespro.ru, andres@anarazel.de, alvherre@alvh.no-ip.org
  Subject: Re: master make check fails on Solaris 10
  In-Reply-To: <5487.1516294381@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox