Re: gcc5: initdb produces gigabytes of _fsm files

What does the ASM look like? It's a fairly quick way to tell whether the
fail is optimization or memory corruption.

Apologies if I'm explaining how to extract albumen to your elderly
relative...

On 12 February 2015 at 23:16, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> I wrote:
> > Christoph Berg <cb(at)df7cb(dot)de> writes:
> >> gcc5 is lurking in Debian experimental, and it's breaking initdb.
>
> > Yeah, I just heard the same about Red Hat as well:
> > https://bugzilla.redhat.com/show_bug.cgi?id=1190978
> > Not clear if it's an outright compiler bug or they've just found some
> > creative new way to make an optimization assumption we're violating.
>
> Apparently, it's the former. See
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1190978#c3
>
> I will be unamused if the gcc boys try to make an argument that they
> did some valid optimization here.
>
> regards, tom lane
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>