[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gcl-devel] Which option to maximize architecture portability on gcl
Re: [Gcl-devel] Which option to maximize architecture portability on gcl-2.6.1
25 Oct 2003 11:22:05 -0400
Gnus/5.09 (Gnus v5.9.0) Emacs/21.2
Greetings! If memory serves, gcc doesn't (yet) emit ISA extension
instructions with any flag setting. If this is the case, what you
have is fine. To be safe, you can redefine the compiler::*cc*
variable as desired (e.g. just omit any march setting).
The stock Debian gcl does not have an march gcc flag setting. If you
build gcl yourself, and have a CFLAGS environment variable set, and
march setting could be thus captured.
David MENTRE <address@hidden> writes:
> Hello Camm,
> I have yet another question on gcl-2.6.1. I noticed that my current
> gcl-2.6.1 on my Celeron machine is using the -march=pentiumpro gcc
> In the eventuality where I would like to compile a static version of
> Axiom portable on any usable x86 machine (pentium or greater), which
> option should I give to gcl configure to have something like -march=i586
> given to gcc?
> In other words, even if I compile Axiom with gcl-2.6.1 on latest Athlon
> or Pentium 4 machine, I would like to have a binary runnable on any x86
> machine (except maybe i486 and i386).
> Gcl-devel mailing list
Camm Maguire address@hidden
"The earth is but one country, and mankind its citizens." -- Baha'u'llah