Re: Complier warnings on mingw gcc 4.5.0

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>, Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Complier warnings on mingw gcc 4.5.0
Date: 2010-12-13 21:29:58
Message-ID: 4D069056.4000409@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12/13/2010 01:12 PM, Tom Lane wrote:
> Andrew Dunstan<andrew(at)dunslane(dot)net> writes:
>> On 12/13/2010 12:01 PM, Tom Lane wrote:
>>> It smells a little bit like an optimization bug. Does dialing down to
>>> -O0 make it go away?
>> Sadly, no. I'm testing downgrading the compiler now.
> Mph. FWIW, I see that my last build of Postgres for Fedora 14 would
> have been with gcc 4.5.1, because that's what F14 is shipping. And
> that passed its regression tests on at least x86 and x86_64. Maybe
> you should pester the mingw folk for a compiler update.
>
>

Further digging shows some weirdness. This doesn't appear to be
compiler-related. I've rolled back all the way to gcc 3.5. It is
triggered by the following line in pg_regress.c, commenting out of which
causes the problem to go away (although of course it causes the
regression tests to fail):

putenv(new_pgoptions);

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2010-12-13 21:32:40 Re: Complier warnings on mingw gcc 4.5.0
Previous Message Jim Nasby 2010-12-13 21:12:04 Re: BufFreelistLock