buildfarm failure after ICC configure change

From: Jeremy Drake <pgsql(at)jdrake(dot)com>
To: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: buildfarm failure after ICC configure change
Date: 2007-09-12 02:47:34
Message-ID: Pine.BSO.4.64.0709111933060.6731@resin.csoft.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I just saw that my buildfarm member (running ICC 9.0 on linux) failed
after the latest change to configure

http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=mongoose&dt=2007-09-11%2020:45:01

I was the one who sent in the first patch to configure to add the check
for ICC, and as I recall at the time, the docs said -fno-strict-aliasing
was the default (which is why I said "not sure if this is needed" in the
comment). I don't know what -fno-alias does, but I think it means that
the program does not do aliasing at all. The docs say "You must
specify -fno-alias if you do not want aliasing to be assumed in the
program" The true option for -fno-strict-aliasing is -ansi-alias-
"disable use of ANSI aliasing rules in optimizations". But this is the
default...

--
Help me, I'm a prisoner in a Fortune cookie file!

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Brendan Jurd 2007-09-12 03:15:29 Add function for quote_qualified_identifier?
Previous Message ITAGAKI Takahiro 2007-09-12 01:47:58 CVS HEAD is broken by flex