| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Marko Karppinen <marko(at)karppinen(dot)fi> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL Performance <pgsql-performance(at)postgresql(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] Sun performance - Major discovery! |
| Date: | 2003-10-14 15:13:52 |
| Message-ID: | Pine.LNX.4.44.0310141708040.22628-100000@peter.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
Marko Karppinen writes:
> GCC sets __FAST_MATH__ even if you counter a -ffast-math with the
> negating flags above. This means that it is not currently possible to
> use the -fast flag when compiling PostgreSQL at all. Instead, you have
> to go through all the flags Apple is setting and only pass on those
> that don't break pg.
That sounds perfectly reasonable to me. Why should we develop elaborate
workarounds for compiler flags that are known to create broken code? I
also want to point out that I'm getting kind of tired of developing more
and more workarounds for sloppy Apple engineering.
--
Peter Eisentraut peter_e(at)gmx(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2003-10-14 15:17:40 | Re: Heading to final release |
| Previous Message | Tom Lane | 2003-10-14 15:00:51 | Re: CREATE USER bug |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-10-14 16:14:19 | Re: [SQL] sql performance and cache |
| Previous Message | Seth Ladd | 2003-10-14 08:18:06 | Re: ways to force index use? |