From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Bison 3.0 updates |
Date: | 2013-07-29 05:28:09 |
Message-ID: | 7520.1375075689@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | buildfarm-members pgsql-hackers |
Stephen Frost <sfrost(at)snowman(dot)net> writes:
> However, I comment on this mainly because anchovy has had issues with
> 9.1 and older for some time, which looks like an issue with GCC 4.8.0.
> Did you happen to resolve or identify what is happening there..?
Yeah, we know about that:
http://www.postgresql.org/message-id/14242.1365200084@sss.pgh.pa.us
The bottom line was:
>> 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. Some other
people argued for (2), but I've not seen any patch emerge from them,
and you can bet I'm not going to do it.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2013-07-29 11:11:13 | Re: Bison 3.0 updates |
Previous Message | Stephen Frost | 2013-07-29 05:19:43 | Re: Bison 3.0 updates |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Gierth | 2013-07-29 05:42:03 | Re: Review: UNNEST (and other functions) WITH ORDINALITY |
Previous Message | Stephen Frost | 2013-07-29 05:19:43 | Re: Bison 3.0 updates |