Optimization
The execution speed of scripts is not typically important in an unmodded game, given the difference in performance between a modern computer and what Fallout was designed for. When you start adding mods to the mix there’s the potential for problems again, since sfall’s global script system means that you can have a large amount of scripts being run every single frame.
sslc -O option
The sfall build of sslc supports a -O command line option to perform an optimization pass over the generated code. This isn’t a magic make-my-code-go-faster bullet; most of what it does is very limited in scope. It’s primary purpose was to strip out the procedures and variables which get automatically pulled into every script that includes define.h, whether you use them or not, and to do something about the additional variables that get created by foreach loops.
There are several levels of optimization available:
-O1- Basic, only removes unreferenced globals variables and procedures, code itself remains untouched.-O2- Full, most code optimizations are on, but only those that were tested on complex scripts.-O3- Experimental, provides most efficiency, but tend to break some complex code due to bugs.
The following optimizations are performed:
- constant expression folding: if an expression depends only on values which are known at compile time, then the expression is replaced by its result.
a := 2 + 2; -> a := 4; +Optimization | sfall Skip to main contentOptimization
The execution speed of scripts is not typically important in an unmodded game, given the difference in performance between a modern computer and what Fallout was designed for. When you start adding mods to the mix there’s the potential for problems again, since sfall’s global script system means that you can have a large amount of scripts being run every single frame.
sslc -O option
The sfall build of sslc supports a
-Ocommand line option to perform an optimization pass over the generated code. This isn’t a magic make-my-code-go-faster bullet; most of what it does is very limited in scope. It’s primary purpose was to strip out the procedures and variables which get automatically pulled into every script that includes define.h, whether you use them or not, and to do something about the additional variables that get created byforeachloops.There are several levels of optimization available:
-O1- Basic, only removes unreferenced variables and procedures, code itself remains untouched.-O2- Full, most code optimizations are on, but only those that were tested on complex scripts.-O3- Experimental, provides the most efficiency, but tends to break some complex code due to bugs.
The following optimizations are performed:
- constant expression folding: if an expression depends only on values which are known at compile time, then the expression is replaced by its result.
a := 2 + 2; -> a := 4; - constant variable initialization: All variables are initialised to some value, (‘0’, if you don’t specify anything else,) so sslc attempts to make use of that fact to remove the first assignment to a variable if the first assignment is a constant expression.
variable a; -> variable a := 4; a := 4; -> - constant propagation: checks for values assigned to variables which can be computed at compile time, and replaces relevant references to the symbol by the constant. The original store is not removed by this optimization. Global variables are considered for this optimization only if they are not marked import or export, and are not assigned to anywhere in the script.
a := 4; -> a := 4; diff --git a/sslc/index.html b/sslc/index.html index cc4073fa..690f957a 100644 --- a/sslc/index.html +++ b/sslc/index.html @@ -1,18 +1,18 @@ -SSLC | sfall Skip to main contentSSLC
This is a modified copy of sslc, that has a few bugfixes from the original, that will recognise and compile the additional script functions provided by sfall, that can also understand some additional syntax, and that has an integrated preprocessor and optimizer.
Unlike the original script compiler, this has not been compiled as a dos program. When using this in place of the original compile.exe but still using p.bat, you need to either get rid of the dos4gw.exe reference from p.bat or replace the original dos4gw.exe with the one in this archive.
If you use Fallout Script Editor, you can extract
compile.exeanddos4gw.exeto its\binaryfolder, or extract them somewhere else and change your preferences in FSE to point there. FSE doesn’t seem to be able to tell when errors occur when using this compiler though, so I’d recommend either using sfall’s script editor instead or compiling by hand if possible.When compiling global or hook scripts for sfall 3.4 or below, you must include the line
procedure start;before any#includefiles that define procedures to avoid a few weird problems. (this is no longer required starting from 3.5)This version of compiler was designed primarily for new sfall functions, but it can safely (and is recommended) to be used with non-sfall scripts as well, as long as you don’t use any of the arrays syntax and any sfall script functions.
The original unmodified sslc source is over here: https://teamx.ru/site_arc/utils/index.html
Command line options
-q don't wait for input on error +SSLC | sfall Skip to main contentSSLC
This is a modified copy of sslc, that has a few bugfixes from the original, that will recognise and compile the additional script functions provided by sfall, that can also understand some additional syntax, and that has an integrated preprocessor and optimizer.
Unlike the original script compiler, this has not been compiled as a DOS program. When using this in place of the original
compile.exebut still usingp.bat, you need to get rid of thedos4gw.exereference fromp.bat.When compiling global or hook scripts for sfall 3.4 or below, you must include the line
procedure start;before any#includefiles that define procedures to avoid a few weird problems. This is no longer required starting from 3.5.This version of compiler was designed primarily for new sfall functions, but it can be safely used (and is recommended) with non-sfall scripts as well.
The original unmodified sslc source is over here: https://teamx.ru/site_arc/utils/index.html
Command line options
-q don't wait for input on error -n no warnings --b backward compatibility mode +-b use backward compatibility mode -l no logo -p preprocess source -P preprocess only (don't generate .int) -F write full file paths in "#line" directives --O optimize code (full by default, see "Optimization" page) --O<N> set specific level of optimization (0 - off, 1 - basic, 2 - full, 3 - experimental) +-O optimize code (full optimization, see "Optimization" page) +-O<N> set specific level of optimization (0 - none, 1 - basic, 2 - full, 3 - experimental) -d print debug messages -D output an abstract syntax tree of the program -o set output path (follows the input file name) -s enable short-circuit evaluation for all AND, OR operators --m<macro[=val]> define a macro named "macro" for conditional compilation --I<path> specify an additional directory to search for include files +-m<macro>[=<val>] define a macro named "macro" for conditional compilation +-I<path> specify an additional directory to search for include filesThe original command line option
-wto turn on warnings no longer has an effect, since warnings are now on by defaultAdditional supported syntax
Syntax which requires sfall for compiled scripts to be interpreted is marked by asterisk (*).
-
Optional arguments in user-defined procedures. You can only use constants for default values. It basically puts those constants in place of omitted arguments.
- new:
procedure test(variable x, variable y := 0, variable z := -1) begin ... end
- new:
-