buildfarm failure after ICC configure change - Mailing list pgsql-hackers

From Jeremy Drake
Subject buildfarm failure after ICC configure change
Date
Msg-id Pine.BSO.4.64.0709111933060.6731@resin.csoft.net
Whole thread Raw
Responses Re: buildfarm failure after ICC configure change
List 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!


pgsql-hackers by date:

Previous
From: ITAGAKI Takahiro
Date:
Subject: CVS HEAD is broken by flex
Next
From: "Brendan Jurd"
Date:
Subject: Add function for quote_qualified_identifier?