Re: Bison 3.0 updates

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Bison 3.0 updates
Date: 2013-08-21 22:33:41
Message-ID: 9657.1377124421@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: buildfarm-members pgsql-hackers

Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> On 2013-07-29 08:02:49 -0400, Tom Lane wrote:
>>> It looks like our choices are (1) teach configure to enable
>>> -fno-aggressive-loop-optimizations if the compiler recognizes it,
>>> or (2) back-port commit 8137f2c32322c624e0431fac1621e8e9315202f9.
>>>
>>> I am in favor of fixing the back branches via (1), because it's less
>>> work and much less likely to break third-party extensions.

> This seems to be the agreed upon course of action, so I've prepared a
> patch including a preliminary commit message. I confirmed that it fixes
> the issue with gcc 4.8 and 9.1 for me.

Committed --- thanks for doing the legwork to check it fixes the problem.

regards, tom lane

In response to

Browse buildfarm-members by date

  From Date Subject
Next Message Marti Raudsepp 2014-01-07 21:48:06 [Pgbuildfarm-members] pgbuildfarm breaks with git 1.8.5
Previous Message Andres Freund 2013-08-21 11:49:33 Re: Bison 3.0 updates

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2013-08-22 00:36:06 Re: plpgsql_check_function - rebase for 9.3
Previous Message Tom Lane 2013-08-21 22:32:13 pgsql: Disable -faggressive-loop-optimizations in gcc 4.8+ for pre-9.2