I was initially using the prebuilt version, but I recompiled v4.0.1 from source (with --enable-single-host and --enable-gcc-opts) and nothing changed.
I just installed the newest version of the Apple Developer Tools, gcc reports: i686-apple-darwin9-gcc-4.0.1 (GCC) 4.0.1 (Apple Inc. build 5465)
Bug has been posted. Tell me if you need any more info about it. http://www.iro.umontreal.ca/~gambit/bugzilla/show_bug.cgi?id=15
James
On 10/29/07, Marc Feeley feeley@iro.umontreal.ca wrote:
Are you using the prebuilt version, or did you compile Gambit yourself? If so, what version of gcc are you using (gcc --version)?
Please post your bug report to http://www.iro.umontreal.ca/~gambit/ bugzilla/ .
Marc
On 29-Oct-07, at 11:48 AM, James Long wrote:
I recently upgraded from OS X Tiger to Leopard and suddenly Gambit's "parsing" time has slowed to a crawl (I have confirmed this on another upgraded machine). I'm not sure if "parsing" is the correct term. But any time where Gambit reads a file and parses the code, gsc/gsi sits there and thrashes the CPU for some time linear to the size of the program. It takes 2.54s just to `include` a 300 line file. Execution speed is not affected.
I tried recompiling Gambit but nothing changed. I know you can compile Gambit with --enable-debug and --enable-profile, but I'm not sure how to debug/profile the system. I think a `make check` does some timing checks, but I waited 2 hours for it to get past the first couple checks (because of the parsing bug) and then gave up.
I wish I could give a better analysis of the problem, but after trying a couple methods of debugging (dtrace, testing different files, etc.), I'm not sure what the problem is. Anyone have Leopard and would be able to shed some light on this?
Gambit-C v4.0.1, OS X 10.5 (Leopard)