This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: testing Octave
- To: Toon Moene <toon at moene dot indiv dot nluug dot nl>
- Subject: Re: testing Octave
- From: Mumit Khan <khan at xraylith dot wisc dot edu>
- Date: Wed, 12 Aug 1998 18:50:28 -0500
- Cc: egcs at cygnus dot com
Toon Moene <toon@moene.indiv.nluug.nl> writes:
>
> Yep, this occurred to me as good testing case too (as would be
> Blitz++; unfortunately, they ask you to join their mailing list to
> obtain the sources, which seems a bit much for testing purposes
> only)
I typically do test blitz since the code is close to what I do. My code
is quite a bit easier on compilers than blitz, and has been working
happily under egcs snapshots for a the past 8 weeks or so. The big
problem with both mine and blitz is that I can't use the optimizer;
eg., if you specify -O[1234] when compiling code using blitz arrays
for example, egcs will quite likely eat up all the RAM. I've seen upto
800M or so, until the system or I kill it. Kai eats up about 100M or
so on the same code using the nastiest optim flags I could find, and
*very slowly* does the job.
> BTW, this is for octave-2.0.9, the newest I could find on the gnu
> mirrors (but I used ftp.nluug.nl; perhaps they're left behind?).
Octave 2.0.9 is just too old. Octave-2.0.13 + the small patch does
work on quite a few platforms that I regularly test. I'm a bit
puzzled with your termcap problem however. Now that octave doesn't
package GNU info reader anymore, at least this problem is solved ;-)
You can for now simply take info out of the makefile and just let
it go ...
Regards,
Mumit