> Hmmm interesting point. I do suppose that when we put in > all the various optimization flags to gcc, we are > implicitely restricting our intended platforms. I dont think so. As you yourself put it, at worst, it will assume that mechanisms will be able to take advantage of the code it produces.
> The only guranteed way to restrict portability is to use > assembly language and then its still usable on a range of > x86. not really. gcc uses -march and -mtune to produce code specifically for the kind of processor you choose. for example, on my laptop with pentium-m, i would use gcc -march pentium-m -mtune pentium-m, and that will produce code for the pentium-m. As opposed to this, binary files meant for distribution would be compiled specifically with -march=i386 or i586, or something to similar effect, which would allow the binary to run on any i386/i586 compatible cpu. Sagar -- Sagar Gokhale -- ______________________________________________________________________ Pune GNU/Linux Users Group Mailing List: (plug-mail@plug.org.in) List Information: http://plug.org.in/mailing-list/listinfo/plug-mail Send 'help' to [EMAIL PROTECTED] for mailing instructions.
