Bug#941495: Internal compiler errror: in decode_addr_const, at varasm.c:2864

Package: gcc-6 Version: 4:6.3.0-18+deb9u1 Severity: important Greetings, gcc is failing on powerpc64le-linux-gnu with a gcc dump. This bug is preventing pgbackrest (and, likely, PostgreSQL itself as of current HEAD, though I haven't had a chance to test it myself) from being able to be built on

Re: gcc-3.4 to unstable for amd64?

* John Goerzen ([EMAIL PROTECTED]) wrote: > On Mon, May 10, 2004 at 05:06:05PM -0400, Stephen Frost wrote: > > * John Goerzen ([EMAIL PROTECTED]) wrote: > > > On Mon, May 10, 2004 at 10:41:02PM +0200, Frederik Schueler wrote: > > > > 3. is pure64 going to be incl

Re: gcc-3.4 to unstable for amd64?

* John Goerzen ([EMAIL PROTECTED]) wrote: > On Mon, May 10, 2004 at 10:41:02PM +0200, Frederik Schueler wrote: > > 3. is pure64 going to be included in sarge? > > No. Honestly, I'm not entirely sure I agree with this, but it does seem unlikely atm. ;) Stephen signature.asc Description:

Re: gcc-3.4 to unstable for amd64?

* Kurt Roeckx ([EMAIL PROTECTED]) wrote: > I've uploaded a new version of gcc-3.4 to alioth. It's currently > still in experimental. > > Since gcc 3.4 includes much better support for amd64 than 3.3 we > would like to see it go to unstable. Some people would like to > see it in unstable on aliot