On Mon, Sep 28, 2015 at 2:34 PM, Josh Berkus <j...@agliodbs.com> wrote: > On 09/28/2015 08:10 AM, Robert Haas wrote: >> -1 on that idea. I really don't think that we should categorically >> decide we don't support higher optimization levels. If the compiler >> has a bug, then the compiler manufacturer should fix it, and it's not >> our fault. If the compiler doesn't have a bug and our stuff is >> blowing up, then we have a bug and should fix it. I suppose there >> could be some grey area but hopefully not too much. > > Or it's PILBChAK. I know Sun-CC used to warn that -O3 was unsuitable for > most programs because it could change behavior.
I'm attempting to decipher this acronym. Problem is located between chair and keyboard? But I don't see how that applies here. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
