-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've compiled programs and used checkinstall to install them. Checkinstall by default copies the rpm's it generates to /usr/src/packages/RPMS/i386 I assume that this means the programs are being compiled for x386, and have not been optimized for my Athlon processor. Is this a correct assumption? If so then what do I need to do at compile time to optimize for the Athlon? Is there a place that this information can be kept (env variable) so that it is automatically taken care of every time I compile a new program? (Note, I'm asking about regular programs, its pretty easy to find out how to optimize the kernel compile) Thanks for your help - -- dh Don't shop at GoogleGear.com! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+glUgBwgxlylUsJARAlf/AJ9KV15Q337FqeAlHEQfPyapEGed8gCeM+bt qrrcUrPtjObOJm6S+Mf4ccg= =j/OV -----END PGP SIGNATURE-----
On Thursday 27 March 2003 02:34, David Herman wrote:
I've compiled programs and used checkinstall to install them. Checkinstall by default copies the rpm's it generates to /usr/src/packages/RPMS/i386
I assume that this means the programs are being compiled for x386, and have not been optimized for my Athlon processor. Is this a correct assumption?
No. You compiled it manually, you didn't use rpm to compile, so rpm doesn't know what optimisation has been used. When you use checkinstall, it just bunches the binaries and other files together in a cpio archive and places it in i386 as a default location. What optimisation is used when you compile manually is determined by the flags you pass to the configure script, as well as the values of the relevant environment variables
If so then what do I need to do at compile time to optimize for the Athlon? Is there a place that this information can be kept (env variable) so that it is automatically taken care of every time I compile a new program?
It depends. Optimisation is a relatively complex area, and there really is no answer valid for all circumstances. The environment variables relevant are CFLAGS for C programs and CXXFLAGS for c++ programs if you use gcc to compile. Values like -O3 and -march=athlon-xp could be used. But the effects of the optimisations varies wildly. Read "man gcc" for a list of the available flags, and http://freshmeat.net/articles/view/730/ as a little introduction to gcc optimisations
(Note, I'm asking about regular programs, its pretty easy to find out how to optimize the kernel compile)
Is it?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 26 March 2003 05:50 pm, Anders Johansson wrote: > On Thursday 27 March 2003 02:34, David Herman wrote: > > I've compiled programs and used checkinstall to install them. > > Checkinstall by default copies the rpm's it generates to > > /usr/src/packages/RPMS/i386 - ----------snip--------------- > What optimisation is used when you compile manually is determined by > the flags you pass to the configure script, as well as the values of > the relevant environment variables > > > If so then what do I need to do at compile time to optimize for the > > Athlon? Is there a place that this information can be kept (env > > variable) so that it is automatically taken care of every time I > > compile a new program? > > It depends. Optimisation is a relatively complex area, and there > really is no answer valid for all circumstances. The environment > variables relevant are CFLAGS for C programs and CXXFLAGS for c++ > programs if you use gcc to compile. Values like -O3 and > -march=athlon-xp could be used. But the effects of the optimisations > varies wildly. Read "man gcc" for a list of the available flags, and > http://freshmeat.net/articles/view/730/ as a little introduction to > gcc optimisations Thanks, thats what I was looking for > > (Note, I'm asking about regular programs, its pretty easy to find > > out how to optimize the kernel compile) > > Is it? Well maybe not easy, but I found it the first time I tried, of course I spent a little time looking at all the options available when I ran make xconfig (processor type and features) I guess stating which processor the kernel is meant to run on (in /usr/src/linux/.config) is not heavy duty optimisation, but thats more or less what I was talking about. Thanks for your answer and pointing me in the right direction. - -- dh Don't shop at GoogleGear.com! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+gqLrBwgxlylUsJARAhnkAJwN9fRy1OOPbuCueyXFOuGHNPW/eQCfcZBB sL5LFO5sjhrRGwMnNbGf1Qo= =rEj8 -----END PGP SIGNATURE-----
participants (2)
-
Anders Johansson
-
David Herman