Horton

Re: master make check fails on Solaris 10

Marina Polyakova <m.polyakova@postgrespro.ru>

View thread View on postgr.es
From: Marina Polyakova <m.polyakova@postgrespro.ru>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: vitus@wagner.pp.ru, Andres Freund <andres@anarazel.de>, pgsql-hackers@postgresql.org, Alvaro Herrera <alvherre@alvh.no-ip.org>
Date: 2018-01-18T17:49:16Z
Lists: pgsql-hackers 
On 18-01-2018 20:34, Tom Lane wrote:
> I wrote:
> ...
> But ... let's not panic, but wait and see the final result of the
> discussion on the gcc PR.  Jakub at least seems to think it ought
> to be a supportable case.
> 
> What you could do in the meantime is work on finding a variation of
> Victor's test that will detect the bug regardless of -O level.
> If we do have hope that future gcc versions will handle this correctly,
> we'll need a better test rather than just summarily dismissing
> host_cpu = sparc.

Thanks, I'll try..

-- 
Marina Polyakova
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

Commits

  1. Extend configure's __int128 test to check for a known gcc bug.

  2. Reorder C includes

  3. Ability to advance replication slots

  4. doc: add JSON acronym

  5. Expression evaluation based aggregate transition invocation.

  6. Change some bogus PageGetLSN calls to BufferGetLSNAtomic

  7. Prevent int128 from requiring more than MAXALIGN alignment.

  8. Rearrange c.h to create a "compiler characteristics" section.

  9. Make OWNER TO subcommand mention consistent