A few questions
Hi folks,
I downloaded rework 13, compiled it, and got the segfaults
on startup. So I went to the web CVS accessand downloaded
what I thought was the latest variable.c, but it didn't
help. Are there other files I need to fix rework 13 ?
Does web CVS really give me the latest stuff ?
While I was compiling rework-13, I noticed that it took
35 minutes on Linux (Mandrake 7.1). It only takes 7 minutes
for my own code in Win32 using the Watcom compiler, and 5
minutes with Borland. I'm running on a 300MHz celeron with
64MB RAM, by the way. Is 35 minutes a reasonable time to
expect with Linux/gcc with that hardware ?
I'm sure I don't remember there being such a marked
difference in compile speed between the two systems
the last time I compiled my own stuff on Linux. The
problem for me, is that the way I tend to work is by
putting #defines in the main header file, so that I
can switch my experimental code in and out. However,
since the header is called by ALL the source files,
if the header changes, make will recompile everything.
However, the upside is that on one of my test simulations,
it seems to run 30% faster than even the Watcom compiler.
I know that the last time I compiled my own stuff on
Linux/gcc, it wasn't significantly different in performance
from the Win32 stuff, and it was Win32 which was faster.
So either gcc produces even better code, now, or you guys
have done something that I don't know about to improve
the speed.
I think I'll try to compile my own code under Linux now,
to see if it's the latest gcc compiler which is making
the difference.
Cheers,
Alan
Partial thread listing: