Fs2 open on Linux/Optimization - Revision history

Niffiwan: The error from -ftree-vectorize was worked around in r9480

2013-09-25T09:30:43Z

The error from -ftree-vectorize was worked around in r9480

← Older revision		Revision as of 09:30, 25 September 2013
Line 12:		Line 12:
	If you want to play it safe, a good set of CFLAGS would be		If you want to play it safe, a good set of CFLAGS would be
	$ ./configure CFLAGS="-march=native -O3 -pipe -fomit-frame-pointer -fno-ident" CXXFLAGS="$CFLAGS"		$ ./configure CFLAGS="-march=native -O3 -pipe -fomit-frame-pointer -fno-ident" CXXFLAGS="$CFLAGS"

	~~Note: it seems that in GCC 4.7.0 (and higher until at least 4.7.2) the -ftree-vectorize flag (part of -O3) causes segfaults in FSO. Therefore you could instead use:~~
	~~$ ./configure CFLAGS="-march=native -O3 -pipe -fomit-frame-pointer -fno-ident -fno-tree-vectorize" CXXFLAGS="$CFLAGS"~~

	In particular, the following flag has been reported to increase the FPS when not looking at nebula: (thanks to oldlaptop for this advice)		In particular, the following flag has been reported to increase the FPS when not looking at nebula: (thanks to oldlaptop for this advice)

Niffiwan at 09:57, 31 December 2012

2012-12-31T09:57:12Z

← Older revision		Revision as of 09:57, 31 December 2012
Line 14:		Line 14:

	Note: it seems that in GCC 4.7.0 (and higher until at least 4.7.2) the -ftree-vectorize flag (part of -O3) causes segfaults in FSO. Therefore you could instead use:		Note: it seems that in GCC 4.7.0 (and higher until at least 4.7.2) the -ftree-vectorize flag (part of -O3) causes segfaults in FSO. Therefore you could instead use:
	$ ./configure CFLAGS="-march=native -O2 -pipe -fomit-frame-pointer -fno-ident -~~finline-functions -funswitch-loops -fpredictive-commoning -fgcse-after-reload -fipa~~-cp-~~clone~~" CXXFLAGS="$CFLAGS"		$ ./configure CFLAGS="-march=native -O3 -pipe -fomit-frame-pointer -fno-ident -fno-tree-vectorize" CXXFLAGS="$CFLAGS"

	In particular, the following flag has been reported to increase the FPS when not looking at nebula: (thanks to oldlaptop for this advice)		In particular, the following flag has been reported to increase the FPS when not looking at nebula: (thanks to oldlaptop for this advice)

Niffiwan at 09:28, 31 December 2012

2012-12-31T09:28:22Z

← Older revision		Revision as of 09:28, 31 December 2012
Line 16:		Line 16:
	$ ./configure CFLAGS="-march=native -O2 -pipe -fomit-frame-pointer -fno-ident -finline-functions -funswitch-loops -fpredictive-commoning -fgcse-after-reload -fipa-cp-clone" CXXFLAGS="$CFLAGS"		$ ./configure CFLAGS="-march=native -O2 -pipe -fomit-frame-pointer -fno-ident -finline-functions -funswitch-loops -fpredictive-commoning -fgcse-after-reload -fipa-cp-clone" CXXFLAGS="$CFLAGS"

	In particular, the following flag has been reported to increase the FPS when not looking at nebula:		In particular, the following flag has been reported to increase the FPS when not looking at nebula: (thanks to oldlaptop for this advice)
	$ -fpredictive-commoning		$ -fpredictive-commoning

Niffiwan at 09:18, 31 December 2012

2012-12-31T09:18:49Z

← Older revision		Revision as of 09:18, 31 December 2012
Line 8:		Line 8:
	<p></p>{{Note\| This step is only for those who want the bleeding-edge source code to compile on their own. You can skip this if you intend to use a provided binary executable.}}		<p></p>{{Note\| This step is only for those who want the bleeding-edge source code to compile on their own. You can skip this if you intend to use a provided binary executable.}}
	Optimizing fs2_open might have little or no effect, or improve performance greatly, I honestly have no clue.<br>		Optimizing fs2_open might have little or no effect, or improve performance greatly, I honestly have no clue.<br>
	You can specify your compiler flags with the configure script, se below.		You can specify your compiler flags with the configure script, see below.
	$ ./configure CFLAGS="<your desired flags>"		$ ./configure CFLAGS="<your desired flags>"
	If you want to play it safe, a good set of CFLAGS would be		If you want to play it safe, a good set of CFLAGS would be
Line 15:		Line 15:
	Note: it seems that in GCC 4.7.0 (and higher until at least 4.7.2) the -ftree-vectorize flag (part of -O3) causes segfaults in FSO. Therefore you could instead use:		Note: it seems that in GCC 4.7.0 (and higher until at least 4.7.2) the -ftree-vectorize flag (part of -O3) causes segfaults in FSO. Therefore you could instead use:
	$ ./configure CFLAGS="-march=native -O2 -pipe -fomit-frame-pointer -fno-ident -finline-functions -funswitch-loops -fpredictive-commoning -fgcse-after-reload -fipa-cp-clone" CXXFLAGS="$CFLAGS"		$ ./configure CFLAGS="-march=native -O2 -pipe -fomit-frame-pointer -fno-ident -finline-functions -funswitch-loops -fpredictive-commoning -fgcse-after-reload -fipa-cp-clone" CXXFLAGS="$CFLAGS"

			In particular, the following flag has been reported to increase the FPS when not looking at nebula:
			$ -fpredictive-commoning

	You should read up on CFLAGS and what they do before trying anything. I recommend you read through these links (adjust the URL as required for your version of GCC).<br>		You should read up on CFLAGS and what they do before trying anything. I recommend you read through these links (adjust the URL as required for your version of GCC).<br>

Niffiwan at 09:17, 31 December 2012

2012-12-31T09:17:35Z

← Older revision		Revision as of 09:17, 31 December 2012
Line 13:		Line 13:
	$ ./configure CFLAGS="-march=native -O3 -pipe -fomit-frame-pointer -fno-ident" CXXFLAGS="$CFLAGS"		$ ./configure CFLAGS="-march=native -O3 -pipe -fomit-frame-pointer -fno-ident" CXXFLAGS="$CFLAGS"

	Note: it seems that in GCC 4.7.0 (and higher until at least 4.7.2) the -ftree-vectorize flag (part of -O3) causes ~~segfaultsin~~ FSO. Therefore you could instead use:		Note: it seems that in GCC 4.7.0 (and higher until at least 4.7.2) the -ftree-vectorize flag (part of -O3) causes segfaults in FSO. Therefore you could instead use:
	$ ./configure CFLAGS="-march=native -O2 -pipe -fomit-frame-pointer -fno-ident -finline-functions -funswitch-loops -fpredictive-commoning -fgcse-after-reload -fipa-cp-clone" CXXFLAGS="$CFLAGS"		$ ./configure CFLAGS="-march=native -O2 -pipe -fomit-frame-pointer -fno-ident -finline-functions -funswitch-loops -fpredictive-commoning -fgcse-after-reload -fipa-cp-clone" CXXFLAGS="$CFLAGS"

Niffiwan at 09:17, 31 December 2012

2012-12-31T09:17:15Z

← Older revision		Revision as of 09:17, 31 December 2012
Line 10:		Line 10:
	You can specify your compiler flags with the configure script, se below.		You can specify your compiler flags with the configure script, se below.
	$ ./configure CFLAGS="<your desired flags>"		$ ./configure CFLAGS="<your desired flags>"
	If you ~~got a i686 and~~ want to play it safe, a good set of CFLAGS would be		If you want to play it safe, a good set of CFLAGS would be
	$ ./configure CFLAGS="-march=~~i686~~ -O3 -pipe -fomit-frame-pointer -fno-ident" CXXFLAGS="$CFLAGS"		$ ./configure CFLAGS="-march=native -O3 -pipe -fomit-frame-pointer -fno-ident" CXXFLAGS="$CFLAGS"
	You should read up on CFLAGS and what they do before trying anything. I recommend you read through these links.<br>
			Note: it seems that in GCC 4.7.0 (and higher until at least 4.7.2) the -ftree-vectorize flag (part of -O3) causes segfaultsin FSO. Therefore you could instead use:
			$ ./configure CFLAGS="-march=native -O2 -pipe -fomit-frame-pointer -fno-ident -finline-functions -funswitch-loops -fpredictive-commoning -fgcse-after-reload -fipa-cp-clone" CXXFLAGS="$CFLAGS"

			You should read up on CFLAGS and what they do before trying anything. I recommend you read through these links (adjust the URL as required for your version of GCC).<br>
	http://gcc.gnu.org/onlinedocs/gcc-4.2.0/gcc/Optimize-Options.html<br>		http://gcc.gnu.org/onlinedocs/gcc-4.2.0/gcc/Optimize-Options.html<br>
	http://gentoo-wiki.com/Safe_Cflags		http://gentoo-wiki.com/Safe_Cflags



	[[Category:FreeSpace Open on Linux\|Optimization]]		[[Category:FreeSpace Open on Linux\|Optimization]]

TopAce at 18:21, 24 September 2008

2008-09-24T18:21:33Z

← Older revision		Revision as of 18:21, 24 September 2008
Line 15:		Line 15:
	http://gcc.gnu.org/onlinedocs/gcc-4.2.0/gcc/Optimize-Options.html<br>		http://gcc.gnu.org/onlinedocs/gcc-4.2.0/gcc/Optimize-Options.html<br>
	http://gentoo-wiki.com/Safe_Cflags		http://gentoo-wiki.com/Safe_Cflags

			[[Category:FreeSpace Open on Linux\|Optimization]]

Ni1s: Fixage

2007-09-03T23:07:10Z

Fixage

← Older revision		Revision as of 23:07, 3 September 2007
Line 11:		Line 11:
	$ ./configure CFLAGS="<your desired flags>"		$ ./configure CFLAGS="<your desired flags>"
	If you got a i686 and want to play it safe, a good set of CFLAGS would be		If you got a i686 and want to play it safe, a good set of CFLAGS would be
	$ ./configure CFLAGS="-march=i686 -O3 -pipe -fomit-frame-pointer -fno-ident" \		$ ./configure CFLAGS="-march=i686 -O3 -pipe -fomit-frame-pointer -fno-ident" CXXFLAGS="$CFLAGS"
	CXXFLAGS="$CFLAGS"
	You should read up on CFLAGS and what they do before trying anything. I recommend you read through these links.<br>		You should read up on CFLAGS and what they do before trying anything. I recommend you read through these links.<br>
	http://gcc.gnu.org/onlinedocs/gcc-4.2.0/gcc/Optimize-Options.html<br>		http://gcc.gnu.org/onlinedocs/gcc-4.2.0/gcc/Optimize-Options.html<br>
	http://gentoo-wiki.com/Safe_Cflags		http://gentoo-wiki.com/Safe_Cflags

Ni1s: Fix Title

2007-09-03T22:52:04Z

Fix Title

← Older revision		Revision as of 22:52, 3 September 2007
Line 1:		Line 1:
	{{Page Navigation\|		{{Page Navigation\|
	BookName=[[~~Fs2 open~~ on Linux]]\|		BookName=[[The fs2_open on Linux Guide]]\|
	CurrentPage=Optimization\|Optimization\|		CurrentPage=Optimization\|Optimization\|
	PrevPage=[[Fs2_open on Linux/Pre-Compile Configuration\|Pre-Compile Configuration]]\|		PrevPage=[[Fs2_open on Linux/Pre-Compile Configuration\|Pre-Compile Configuration]]\|

Ni1s: Page N

2007-09-03T22:02:58Z

Page N

← Older revision		Revision as of 22:02, 3 September 2007
Line 1:		Line 1:
			{{Page Navigation\|
			BookName=[[Fs2 open on Linux]]\|
			CurrentPage=Optimization\|Optimization\|
			PrevPage=[[Fs2_open on Linux/Pre-Compile Configuration\|Pre-Compile Configuration]]\|
			NextPage=[[Fs2_open on Linux/Compiling\|Compiling]]}}
			<p></p>
	{{Warning\| If you compile a debug build, don't use the <b>-fomit-frame-pointer</b> and <b>-fno-ident</b> compiler flags, as it will make debugging impossible.}}		{{Warning\| If you compile a debug build, don't use the <b>-fomit-frame-pointer</b> and <b>-fno-ident</b> compiler flags, as it will make debugging impossible.}}
	<p></p>{{Note\| This step is only for those who want the bleeding-edge source code to compile on their own. You can skip this if you intend to use a provided binary executable.}}		<p></p>{{Note\| This step is only for those who want the bleeding-edge source code to compile on their own. You can skip this if you intend to use a provided binary executable.}}

← Older revision		Revision as of 22:52, 3 September 2007
Line 1:		Line 1:
	{{Page Navigation\|		{{Page Navigation\|
	BookName=[[~~Fs2 open~~ on Linux]]\|		BookName=[[The fs2_open on Linux Guide]]\|
	CurrentPage=Optimization\|Optimization\|		CurrentPage=Optimization\|Optimization\|
	PrevPage=[[Fs2_open on Linux/Pre-Compile Configuration\|Pre-Compile Configuration]]\|		PrevPage=[[Fs2_open on Linux/Pre-Compile Configuration\|Pre-Compile Configuration]]\|

← Older revision		Revision as of 22:02, 3 September 2007
Line 1:		Line 1:
			{{Page Navigation\|
			BookName=[[Fs2 open on Linux]]\|
			CurrentPage=Optimization\|Optimization\|
			PrevPage=[[Fs2_open on Linux/Pre-Compile Configuration\|Pre-Compile Configuration]]\|
			NextPage=[[Fs2_open on Linux/Compiling\|Compiling]]}}
			<p></p>
	{{Warning\| If you compile a debug build, don't use the <b>-fomit-frame-pointer</b> and <b>-fno-ident</b> compiler flags, as it will make debugging impossible.}}		{{Warning\| If you compile a debug build, don't use the <b>-fomit-frame-pointer</b> and <b>-fno-ident</b> compiler flags, as it will make debugging impossible.}}
	<p></p>{{Note\| This step is only for those who want the bleeding-edge source code to compile on their own. You can skip this if you intend to use a provided binary executable.}}		<p></p>{{Note\| This step is only for those who want the bleeding-edge source code to compile on their own. You can skip this if you intend to use a provided binary executable.}}