From: Richard Freeman <rich@thefreemanclan.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Compiling mozilla/firefox with -O2
Date: Mon, 07 Nov 2005 14:24:24 -0500 [thread overview]
Message-ID: <436FA9E8.3060206@thefreemanclan.net> (raw)
In-Reply-To: <436F70C0.1040303@telia.com>
[-- Attachment #1: Type: text/plain, Size: 967 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Simon Strandman wrote:
>
> So please test compiling firefox and other mozilla apps with -O2 and
> respond to that bug so this can be fixed!
>
I edited the eclass to hard code in -Os and firefox built fine, and so
far appears to run fine. I confirmed that -Os was used in the actual
emerge log so it didn't get filtered out. So, that is a good sign.
Perhaps we can be a little more liberal with the flags in the future.
I'll have to try it out with thunderbird. Too bad I don't have memory
usage stats on firefox before the upgrade. I'll have to generate those
for thunderbird. I love -Os since RAM tends to be more limiting than
CPU for most applications.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFDb6nog2bN8aFizRkRAuf+AJsGr/nPSTTOqEgw2+klgfZOMqxtegCeJJl/
gxWGTcZXl3z/cbWXOXeFNr4=
=x/Iz
-----END PGP SIGNATURE-----
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 4275 bytes --]
next prev parent reply other threads:[~2005-11-07 19:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-07 15:20 [gentoo-amd64] Compiling mozilla/firefox with -O2 Simon Strandman
2005-11-07 16:07 ` David Edge
2005-11-07 19:07 ` Simon Strandman
2005-11-07 20:01 ` David Edge
2005-11-08 20:07 ` Simon Strandman
2005-11-08 20:45 ` David Edge
2005-11-07 16:14 ` [gentoo-amd64] " Duncan
2005-11-07 19:09 ` Simon Strandman
2005-11-07 19:24 ` Richard Freeman [this message]
2005-11-08 20:06 ` [gentoo-amd64] " Simon Strandman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=436FA9E8.3060206@thefreemanclan.net \
--to=rich@thefreemanclan.net \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox