Re: makemake.in configuration (os--hw) -- what default settings?

Jörg wrote:
> OTOH, the default "portability" (which includes -DWIDE internally) costs 33% performance
> against the best (so far) optimized result (as seen by make benchmark), on my 32bit
> machine.

The performance is not essential for the --enable-portability setting. The
bit-rot rate is what matters for this setting. Half a year ago, when I
introduced --enable-portability, it was the *only* working configuration on
about 1/3 of the platforms. Optimizations can have bugs or can make assumptions
that no longer hold 5 years later. This is the issue that --enable-portability
solves.

> >The first thing to check is whether the address range in processes on your Mac is similar
> >enough as the one on Mac OS X/x86_64 with 32-bit ABI, that I have access to. See the
> >unix/PLATFORMS file, section "Address space layout".
> AFAICT, it looked identical

Good, then you can proceed to the next step I detailed.

> Are you aware that adding or not -O is useless, because somewhere down the line,
> -O2 and lots of -W get added anyway, when compiling clisp?

Indeed. Adding -O2 when -O was specified in CFLAGS may be a violation of the
GNU standards, but it is a low-priority one, IMO.

Bruno


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
clisp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-devel