Re: [PATCH] PostgreSQL fails to build with 32bit MinGW-w64

From: Mark Cave-Ayland <mark(dot)cave-ayland(at)siriusit(dot)co(dot)uk>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] PostgreSQL fails to build with 32bit MinGW-w64
Date: 2011-12-14 14:44:24
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 14/12/11 13:59, Andrew Dunstan wrote:

> Hmm. Yeah, if I remove -O0 and instead set CFLAGS to -ffloat-store the
> error goes away.
> So, would we want to use that just for this file, or for the whole build?

Well the latest documentation for gcc gives 2 options: -ffloat-store and
-fexcess-precision=<style> which are documented at

For PostGIS we only applied the flags for specific files, because of
severe performance warnings in older versions of the gcc documentation
such as this: I have no
idea whether these warnings still hold true or not for more modern
compiler versions.

ISTM that the best solution would be to determine whether or not
-fexcess-precision=standard does the right thing (and also determine the
performance hit) or take a look at the "excess precision" notes in the
older documentation to see if parts of the code can be rearranged to
eliminate the effect.



Mark Cave-Ayland - Senior Technical Architect
PostgreSQL - PostGIS
Sirius Corporation plc - control through freedom
t: +44 870 608 0063

Sirius Labs:

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2011-12-14 14:48:26 Re: pg_dump --exclude-table-data
Previous Message Andrew Dunstan 2011-12-14 14:31:45 Re: pg_dump --exclude-table-data