Re: initdb failure on Debian sid/mips64el in EventTriggerEndCompleteQuery

From: Christoph Berg <myon(at)debian(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: initdb failure on Debian sid/mips64el in EventTriggerEndCompleteQuery
Date: 2017-09-04 08:22:12
Message-ID: 20170904082211.b2i4h2g4e6vrljrk@msg.df7cb.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Re: Tom Lane 2017-08-13 <14677(dot)1502638689(at)sss(dot)pgh(dot)pa(dot)us>
> Christoph Berg <myon(at)debian(dot)org> writes:
> > Seems to be a gcc-7 problem affecting several packages on mips64el:
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871514
>
> Hm, unless there is a use of sigsetjmp earlier in that clamav
> routine, I would not assume that that's the same issue. The bug
> I suspect we are looking at here is very specific to sigsetjmp
> callers: it usually amounts to the compiler unsafely trying to
> use the same temporary location for multiple purposes.

It appears to have been the same issue - non-long ints spilled on the
stack and loaded back as long int:

Changes:
gcc-7 (7.2.0-3) unstable; urgency=high
.
* Update to SVN 20170901 (r251583) from the gcc-7-branch.
- Fix PR target/81504 (PPC), PR c++/82040.
* Apply proposed patch for PR target/81803 (James Cowgill), conditionally
for mips* targets. Closes: #871514.

The package built successfully on mips64el now.

Christoph

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2017-09-04 08:49:40 Release Note changes
Previous Message Michael Paquier 2017-09-04 08:17:19 Re: [BUGS] Bug in Physical Replication Slots (at least 9.5)?