Compiling flags for Mozilla Firefox
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I installed the rpm from ftp.suse.com of Mozilla Firefox 1.0 for SuSE 9.2 x86_64. Writing about:buildconfig in the URL box, I noticed that it was compiled without the -march=k8 or the -m64 flags. I then downloaded the src.rpm and compiled it with this flags - no problems at all. I would like to know why it wasn't compiled at first place with these flags, as in the man page of gcc it says that these flags turn on a set of options specific for the AMD64 processors. Best regards, Alex -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFB4Dv1PjVgz/mpp6YRAgXvAKCfemoheI46FQljhQg3STjjJyrkGACdFbKo mcCmn2AcBVSzwbRFMVyaB0I= =MAfO -----END PGP SIGNATURE-----
On Sat, Jan 08, 2005 at 08:00:53PM +0000, Alexandre Moutinho Santos wrote:
I installed the rpm from ftp.suse.com of Mozilla Firefox 1.0 for SuSE 9.2 x86_64. Writing about:buildconfig in the URL box, I noticed that it was compiled without the -march=k8 or the -m64 flags. I then downloaded the src.rpm and compiled it with this flags - no problems at all.
Both -m64 and -march=k8 are default on x86-64 Linux.
I would like to know why it wasn't compiled at first place with these flags, as in the man page of gcc it says that these flags turn on a set of options specific for the AMD64 processors.
It's not correct. -Andi
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Andi Kleen wrote: | On Sat, Jan 08, 2005 at 08:00:53PM +0000, Alexandre Moutinho Santos | wrote: |> I installed the rpm from ftp.suse.com of Mozilla Firefox 1.0 for |> SuSE 9.2 x86_64. Writing about:buildconfig in the URL box, I |> noticed that it was compiled without the -march=k8 or the -m64 |> flags. I then downloaded the src.rpm and compiled it with this |> flags - no problems at all. | | Both -m64 and -march=k8 are default on x86-64 Linux. | |> I would like to know why it wasn't compiled at first place with |> these flags, as in the man page of gcc it says that these flags |> turn on a set of options specific for the AMD64 processors. | | It's not correct. | | -Andi So, you are saying that everytime I compile a program in SuSE 9.2 x86_64 the flags specific for the 64 bits are there by default. Ok. Alex -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFB4FZIPjVgz/mpp6YRAroSAJ4uS4NUEibznOWzGGHTmaXU4UyooACgkl/N ve01IaLHe723BjJCVJnNoDQ= =mrOh -----END PGP SIGNATURE-----
Alexandre Moutinho Santos
Andi Kleen wrote: | On Sat, Jan 08, 2005 at 08:00:53PM +0000, Alexandre Moutinho Santos | wrote: |> I installed the rpm from ftp.suse.com of Mozilla Firefox 1.0 for |> SuSE 9.2 x86_64. Writing about:buildconfig in the URL box, I |> noticed that it was compiled without the -march=k8 or the -m64 |> flags. I then downloaded the src.rpm and compiled it with this |> flags - no problems at all. | | Both -m64 and -march=k8 are default on x86-64 Linux. | |> I would like to know why it wasn't compiled at first place with |> these flags, as in the man page of gcc it says that these flags |> turn on a set of options specific for the AMD64 processors. | | It's not correct. | | -Andi So, you are saying that everytime I compile a program in SuSE 9.2 x86_64 the flags specific for the 64 bits are there by default. Ok.
Yes, exactly. Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Sat, Jan 08, 2005 at 08:00:53PM +0000, Alexandre Moutinho Santos wrote:
Hello, I installed the rpm from ftp.suse.com of Mozilla Firefox 1.0 for SuSE 9.2 x86_64. Writing about:buildconfig in the URL box, I noticed that it was compiled without the -march=k8 or the -m64 flags. I then downloaded the src.rpm and compiled it with this flags - no problems at all. I would like to know why it wasn't compiled at first place with these flags, as in the man page of gcc it says that these flags turn on a set of options specific for the AMD64 processors. Best regards, Alex
-m64 is the default (generate 64bit code). -march=k8 ... cannot really find out the default, but it does not matter much yet, because there are not much differences in the x86_64 machines yet. Ciao, Marcus
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Marcus Meissner wrote: | On Sat, Jan 08, 2005 at 08:00:53PM +0000, Alexandre Moutinho Santos | wrote: |> Hello, I installed the rpm from ftp.suse.com of Mozilla Firefox |> 1.0 for SuSE 9.2 x86_64. Writing about:buildconfig in the URL |> box, I noticed that it was compiled without the -march=k8 or the |> -m64 flags. I then downloaded the src.rpm and compiled it with |> this flags - no problems at all. I would like to know why it |> wasn't compiled at first place with these flags, as in the man |> page of gcc it says that these flags turn on a set of options |> specific for the AMD64 processors. Best regards, Alex | | -m64 is the default (generate 64bit code). -march=k8 ... cannot | really find out the default, but it does not matter much yet, | because there are not much differences in the x86_64 machines yet. | | Ciao, Marcus The gcc manual states the following for the -march: k8, opteron, athlon64, athlon-fx ~ AMD K8 core based CPUs with x86-64 instruction set support. ~ (This supersets MMX, SSE, SSE2, 3dNOW!, enhanced 3dNOW! and ~ 64-bit instruction set extensions.) Alex -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFB4Fd1PjVgz/mpp6YRAliKAKCbvxjmITwo4GcAalIGJ3Ppj0AJUgCfRhdo tCKcBNMKtnr2Lix3mhDaYEs= =lHdT -----END PGP SIGNATURE-----
participants (4)
-
Alexandre Moutinho Santos
-
Andi Kleen
-
Andreas Jaeger
-
Marcus Meissner