[Fx] Swiftfox [Linux] [3.5.3]

[RabidPenguin]

Optimized Mozilla Firefox Build for Linux

www.getswiftfox.com

Description
An optimized build of Mozilla Firefox for AMD and Intel processors.

Download
Swiftfox 3.5.3

Unofficial Artwork
Jairo Boudewyn
www.jairoboudewyn.com

[RabidPenguin]

Both branches and the trunk have new builds for today.

[RabidPenguin]

New builds are done for the trunk and 1.8 branch.

[RabidPenguin]

All new builds for today.

[RabidPenguin]

The 1.8 branch build is updated for today.

[RabidPenguin]

New trunk builds today.

[RabidPenguin]

Completed new trunk and 1.8 branch builds today. I also uploaded some Intel and older AMD builds for testing. So if anyone with the applicable chips tests them, thanks!

[SpeedBoy]

Yesterday i started trying your swiftfox 1.5.0.1 p4 build and i'm loving it. It is really fast and not a single crash yet. A really great build man. I hope you can find some time to make some more P4 builds in the future.

[RabidPenguin]

Thanks SpeedBoy glad to hear it works well for you. I will definitely do more P4 builds in the future. If anyone has a need for other builds let me know.

[RabidPenguin]

New trunk build for AMD64 is available.

[Serotonin]

Can you make an rpm?

OS: Fedora Core 5 (x86_64)
MB: Tyan K8WE (SCSI) (s2895)
CPU: Opteron 275 2.2GHz

[daihard]

Can you make an rpm?

OS: Fedora Core 5 (x86_64)
MB: Tyan K8WE (SCSI) (s2895)
CPU: Opteron 275 2.2GHz

I'm sure he can. All he has to do is take the official Fedora Core 5 SRPM and rebuild it using his own optimization flags. Not that I'm trying to make the proces sound like an easy one, but I'm sure someone of his calibre has no problem doing that.

Now, RabidPenguin, would you mind sharing your knowledge with me? I did make my own FC5 RPM (for Athlon 64 but 32-bit) using my own flags, as below:

Code: Select all

-O3 -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=athlon64 -msse2 -fasynchronous-unwind-tables

Do they look okay to you? Most of the flags are used by FC5 by default, so I am hesitant to get rid of them (i.e. Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4). Any feedback would be appreciated.

[RabidPenguin]

Can you make an rpm?

OS: Fedora Core 5 (x86_64)
MB: Tyan K8WE (SCSI) (s2895)
CPU: Opteron 275 2.2GHz

Are you looking for a 64-bit build? My AMD64 builds are 32-bit, but I will look into what it would take to do an RPM. I haven't use Red Hat since version 8 so I am a bit rusty on rpm building.

[daihard]

Can you make an rpm?

OS: Fedora Core 5 (x86_64)
MB: Tyan K8WE (SCSI) (s2895)
CPU: Opteron 275 2.2GHz

Are you looking for a 64-bit build? My AMD64 builds are 32-bit, but I will look into what it would take to do an RPM. I haven't use Red Hat since version 8 so I am a bit rusty on rpm building.

Just FYI, looks like you need the version of GCC that has 64-bit mode compiled in. I am running FC5 (32-bit) on an Athlon 64 machine. I tried to compile a test program using "-m64" but got the following error.

Code: Select all

test.c:1: sorry, unimplemented: 64-bit mode not compiled in

[RabidPenguin]

I'm sure he can. All he has to do is take the official Fedora Core 5 SRPM and rebuild it using his own optimization flags. Not that I'm trying to make the proces sound like an easy one, but I'm sure someone of his calibre has no problem doing that.

Aww you're making me blush. Hey Dai good to see you again, haven't seen you around much lately. Though admittedly I haven't been around here much lately myself so maybe that has something to do with it.

Now, RabidPenguin, would you mind sharing your knowledge with me? I did make my own FC5 RPM (for Athlon 64 but 32-bit) using my own flags, as below:

Code: Select all

-O3 -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=athlon64 -msse2 -fasynchronous-unwind-tables

Do they look okay to you? Most of the flags are used by FC5 by default, so I am hesitant to get rid of them (i.e. Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4). Any feedback would be appreciated.

Well Dai I am no gcc expert but for the most part it looks fine. I think you could safely leave out Wp. In fact, according the the gcc man page you probably should.

You can use -Wp,option to bypass the compiler driver and pass option directly through to the preprocessor. If option contains commas, it is split into multiple options at the commas. However, many options are modified, translated or interpreted by the compiler driver before being passed to the preprocessor, and -Wp forcibly bypasses this phase. The preprocessor's direct interface is undocumented and subject to change, so whenever possible you should avoid using -Wp and let the driver handle the options instead.

-D_FORTIFY_SOURCE=2 and -fstack-protector provide some buffer overflow protection. --param=ssp-buffer-size=4 is used in conjunction with -fstack-protector.