egcs experimentation results
For work-related reasons I recently had to install egcs 1.1.2 here.
I thought I'd try Postgres with it, since we have at least two reports
of problems seen only with egcs:
1. The business about char and short parameters to functions
called through fmgr;
2. Oleg's report of instability seen only with egcs and -O.
The upshot is that I found a few minor glitches in the configure
script, and cleaned up two or three insignificant warnings that
egcs generates but gcc doesn't. I was *not* able to duplicate
any instability using either -O2 or -O3. The regression tests all
pass, and Oleg's fifteen-way join test is happy too.
This is on an HP-PA box, which is not the same as the PowerPC that
problem #1 was reported on, but is likewise a RISC architecture.
So I was hopeful I would see that problem here.
So, now what? From talking to Bruce off-list, I know that he's not
eager to make changes as extensive as problem #1 appears to require
on the strength of just one unconfirmed trouble report. I think I
have to agree...
regards, tom lane
On Sun, 30 May 1999, Tom Lane wrote:
Date: Sun, 30 May 1999 11:47:15 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-hackers@postgreSQL.org
Subject: [HACKERS] egcs experimentation resultsFor work-related reasons I recently had to install egcs 1.1.2 here.
I thought I'd try Postgres with it, since we have at least two reports
of problems seen only with egcs:
1. The business about char and short parameters to functions
called through fmgr;
2. Oleg's report of instability seen only with egcs and -O.
Tom,
the problem seems gone away after cleaning computer box with vacuum
machine and replacing cooler :-! This could be goind to FAQ :-)
The upshot is that I found a few minor glitches in the configure
script, and cleaned up two or three insignificant warnings that
egcs generates but gcc doesn't. I was *not* able to duplicate
any instability using either -O2 or -O3. The regression tests all
pass, and Oleg's fifteen-way join test is happy too.
I just run 60 tables join and it took 17 minutes
on my P200, 64Mb RAM and postgres compiled with -O2 -mpentium
I don't know how it's fast but it works ! Just explain requires
15:30 minutes.
Oleg
This is on an HP-PA box, which is not the same as the PowerPC that
problem #1 was reported on, but is likewise a RISC architecture.
So I was hopeful I would see that problem here.So, now what? From talking to Bruce off-list, I know that he's not
eager to make changes as extensive as problem #1 appears to require
on the strength of just one unconfirmed trouble report. I think I
have to agree...regards, tom lane
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83
On 30-May-99 Oleg Bartunov wrote:
On Sun, 30 May 1999, Tom Lane wrote:
Date: Sun, 30 May 1999 11:47:15 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-hackers@postgreSQL.org
Subject: [HACKERS] egcs experimentation resultsFor work-related reasons I recently had to install egcs 1.1.2 here.
I thought I'd try Postgres with it, since we have at least two reports
of problems seen only with egcs:
1. The business about char and short parameters to functions
called through fmgr;
2. Oleg's report of instability seen only with egcs and -O.Tom,
the problem seems gone away after cleaning computer box with vacuum
machine and replacing cooler :-! This could be goind to FAQ :-)
I use egcs on FreeBSD and Solaris x86 about a year and have no problems at all.
There was some compilation problems of libpg++, but it seems to be fixed.
---
Dmitry Samersoff, dms@wplus.net, ICQ:3161705
http://devnull.wplus.net
* There will come soft rains ...