Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ec3w1-0001Bb-ME for pgsql-hackers@arkaria.postgresql.org; Thu, 18 Jan 2018 06:44:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ec3w1-00058T-As for pgsql-hackers@arkaria.postgresql.org; Thu, 18 Jan 2018 06:44:25 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1ec3sh-0000js-68 for pgsql-hackers@lists.postgresql.org; Thu, 18 Jan 2018 06:40:59 +0000 Received: from mx.wagner.pp.ru ([2a01:4f8:c17:2e5b::2]) by makus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ec3sd-0003XH-9w for pgsql-hackers@lists.postgresql.org; Thu, 18 Jan 2018 06:40:57 +0000 Received: from fafnir.local.vm (unknown [93.174.131.141]) by mx.wagner.pp.ru (Postfix) with ESMTPSA id 06F55E0184 for ; Thu, 18 Jan 2018 09:40:49 +0300 (MSK) Date: Thu, 18 Jan 2018 09:40:49 +0300 From: Victor Wagner To: pgsql-hackers@lists.postgresql.org Subject: Re: master make check fails on Solaris 10 Message-ID: <20180118094049.10293b39@fafnir.local.vm> In-Reply-To: <31743.1516206789@sss.pgh.pa.us> References: <0d3a9fa264cebe1cb9966f37b7c06e86@postgrespro.ru> <20180111173938.jimybeayp2u5mmup@alap3.anarazel.de> <31a342fa6a025a8bdfc5b8b19c29d56d@postgrespro.ru> <1232.1515780057@sss.pgh.pa.us> <15299.1515867055@sss.pgh.pa.us> <18209.1516059711@sss.pgh.pa.us> <90ab676392c8f9c84431976147097cf0@postgrespro.ru> <17897.1516202926@sss.pgh.pa.us> <1c70bab595a37ffa3a7fafea29fa6f55@postgrespro.ru> <31743.1516206789@sss.pgh.pa.us> X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Wed, 17 Jan 2018 11:33:09 -0500 Tom Lane wrote: > Attached is a draft patch to incorporate Victor's slimmed-down test > into configure. If you have a chance, could you confirm it does > the right thing on your Sparc machine? It seems that what it does is not exactly a right thing. I've applied it to commit 9c7d06d60680 in master and see following $ ./configure CC="gcc -m64" [skip] checking for __int128... yes checking for __int128 alignment bug... ok checking alignment of PG_INT128_TYPE... 16 checking for builtin __sync char locking functions... yes [skip] As far as I understand your patch, there should be: checking for __int128 alignment bug... broken Then in the pg_config.h I see /* The normal alignment of `PG_INT128_TYPE', in bytes. */ #define ALIGNOF_PG_INT128_TYPE 16 /* Define to the name of a signed 128-bit integer type. */ #define PG_INT128_TYPE __int128 However, make check passes. There are two things which puzzle me 1. Why test program doesn't detect bug. If I cut'n'paste it from configure, compile with flags, cut'n'pasted from config log and run, it returns 1. But configure tells that all is ok 2. If bug exist and is not detected by configure why make check passes. We, Marina and I would continue investigation.