GBDK 2020 Docs  4.1.1
API Documentation for GBDK 2020
Coding Guidelines

Learning C / C fundamentals

Writing games and other programs with GBDK will be much easier with a basic understanding of the C language. In particular, understanding how to use C on "Embedded Platforms" (small computing systems, such as the Game Boy) can help you write better code (smaller, faster, less error prone) and avoid common pitfalls.

General C tutorials

Embedded C introductions

Game Boy games in C

Understanding the hardware

In addition to understanding the C language it's important to learn how the Game Boy hardware works. What it is capable of doing, what it isn't able to do, and what resources are available to work with. A good way to do this is by reading the Pandocs and checking out the awesome_gb list.

Writing optimal C code for the Game Boy and SDCC

The following guidelines can result in better code for the Game Boy, even though some of the guidance may be contrary to typical advice for general purpose computers that have more resources and speed.

Tools

GBTD / GBMB, Arrays and the "const" keyword

Important: The old GBTD/GBMB fails to include the const keyword when exporting to C source files for GBDK. That causes arrays to be created in RAM instead of ROM, which wastes RAM, uses a lot of ROM to initialize the RAM arrays and slows the compiler down a lot.

__Use of toxa's updated GBTD/GBMB is highly recommended.__

If you wish to use the original tools, you must add the const keyword every time the graphics are re-exported to C source files.

Variables

  • Use 8-bit values as much as possible. They will be much more efficient and compact than 16 and 32 bit types.
  • Prefer unsigned variables to signed ones: the code generated will be generally more efficient, especially when comparing two values.
  • Use explicit types so you always know the size of your variables. int8_t, uint8_t, int16_t, uint16_t, int32_t, uint32_t and bool. These are standard types defined in stdint.h (#include <stdint.h>) and stdbool.h (#include <stdbool.h>).
  • Global and local static variables are generally more efficient than local non-static variables (which go on the stack and are slower and can result in slower code).
  • const keyword: use const for arrays, structs and variables with read-only (constant) data. It will reduce ROM, RAM and CPU usage significantly. Non-const values are loaded from ROM into RAM inefficiently, and there is no benefit in loading them into the limited available RAM if they aren't going to be changed.
  • Here is how to declare const pointers and variables:
  • For calculated values that don't change, pre-compute results once and store the result. Using lookup-tables and the like can improve speed and reduce code size. Macros can sometimes help. It may be beneficial to do the calculations with an outside tool and then include the result as C code in a const array.
  • Use an advancing pointer (someStruct->var = x; someStruct++) to loop through arrays of structs instead of using indexing each time in the loop someStruct[i].var = x.
  • When modifying variables that are also changed in an Interrupt Service Routine (ISR), wrap them the relevant code block in a __critical { } block. See http://sdcc.sourceforge.net/doc/sdccman.pdf#section.3.9
  • When using constants and literals the U, L and UL postfixes can be used.
    • U specifies that the constant is unsigned
    • L specifies that the constant is long.
    • NOTE: In SDCC 3.6.0, the default for char changed from signed to unsigned. The manual says to use --fsigned-char for the old behavior, this option flag is included by default when compiling through lcc.

  • A fixed point type (fixed) is included with GBDK when precision greater than whole numbers is required for 8 bit range values (since floating point is not included in GBDK).

See the "Simple Physics" sub-pixel example project.

Code example:

  fixed player[2];
  ...
  // Modify player position using its 16 bit representation
  player[0].w += player_speed_x;
  player[1].w += player_speed_y;
  ...
  // Use only the upper 8 bits for setting the sprite position
  move_sprite(0, player[0].h ,player[1].h);

Code structure

  • Do not #include .c source files into other .c source files. Instead create .h header files for them and include those. https://www.tutorialspoint.com/cprogramming/c_header_files.htm
  • Instead of using a blocking delay() for things such as sprite animations/etc (which can prevent the rest of the game from continuing) many times it's better to use a counter which performs an action once every N frames. sys_time may be useful in these cases.
  • When processing for a given frame is done and it is time to wait before starting the next frame, wait_vbl_done() can be used. It uses HALT to put the CPU into a low power state until processing resumes. The CPU will wake up and resume processing at the end of the current frame when the Vertical Blanking interrupt is triggered.
  • Minimize use of multiplication, modulo with non-powers of 2, and division with non-powers of 2. These operations have no corresponding CPU instructions (software functions), and hence are time costly.
    • SDCC has some optimizations for:
      • Division by powers of 2. For example n /= 4u will be optimized to n >>= 2.
      • Modulo by powers of 2. For example: (n % 8) will be optimized to (n & 0x7).
    • If you need decimal numbers to count or display a score, you can use the GBDK BCD (binary coded decimal) number functions. See: bcd.h and the BCD example project included with GBDK.
  • Avoid long lists of function parameters. Passing many parameters can add overhead, especially if the function is called often. Globals and local static vars can be used instead when applicable.
  • Use inline functions if the function is short (with the inline keyword, such as inline uint8_t myFunction() { ... }).
  • Do not use recursive functions.

GBDK API/Library

  • stdio.h: If you have other ways of printing text, avoid including stdio.h and using functions such as printf(). Including it will use a large number of the background tiles for font characters. If stdio.h is not included then that space will be available for use with other tiles instead.
  • drawing.h: The Game Boy graphics hardware is not well suited to frame-buffer style graphics such as the kind provided in drawing.h. Due to that, most drawing functions (rectangles, circles, etc) will be slow . When possible it's much faster and more efficient to work with the tiles and tile maps that the Game Boy hardware is built around.
  • waitpad() and waitpadup check for input in a loop that doesn't HALT at all, so the CPU will be maxed out until it returns. One alternative is to write a function with a loop that checks input with joypad() and then waits a frame using wait_vbl_done() (which idles the CPU while waiting) before checking input again.
  • joypad(): When testing for multiple different buttons, it's best to read the joypad state once into a variable and then test using that variable (instead of making multiple calls).

Toolchain

  • See SDCC optimizations: http://sdcc.sourceforge.net/doc/sdccman.pdf#section.8.1
  • Use profiling. Look at the ASM generated by the compiler, write several versions of a function, compare them and choose the faster one.
  • Use the SDCC --max-allocs-per-node flag with large values, such as 50000. --opt-code-speed has a much smaller effect.
    • GBDK-2020 (after v4.0.1) compiles the library with --max-allocs-per-node 50000, but it must be turned on for your own code.
      (example: lcc ... -Wf--max-allocs-per-node50000 or sdcc ... --max-allocs-per-node 50000).
    • The other code/speed flags are --opt-code-speed or --opt-code-size.
  • Use current SDCC builds from http://sdcc.sourceforge.net/snap.php
    The minimum required version of SDCC will depend on the GBDK-2020 release. See GBDK Release Notes
  • Learn some ASM and inspect the compiler output to understand what the compiler is doing and how your code gets translated. This can help with writing better C code and with debugging.

Constants, Signed-ness and Overflows

There are a some scenarios where the compiler will warn about overflows with constants. They often have to do with mixed signedness between constants and variables. To avoid problems use care about whether or not constants are explicitly defined as unsigned and what type of variables they are used with.

WARNING: overflow in implicit constant conversion

  • A constant can be used where the the value is too high (or low) for the storage medium causing an value overflow.
    • For example this constant value is too high since the max value for a signed 8 bit char is 127.
       #define TOO_LARGE_CONST 255
       int8_t signed_var = TOO_LARGE_CONST;
      
  • This can also happen when constants are not explicitly declared as unsigned (and so may get treated by the compiler as signed) and then added such that the resulting value exceeds the signed maximum.
    • For example, this results in an warning even though the sum total is 254 which is less than the 255, the max value for a unsigned 8 bit char variable.
        #define CONST_UNSIGNED 127u
        #define CONST_SIGNED 127
        uint8_t unsigned_var = (CONST_SIGNED + CONST_UNSIGNED);
      
    • It can be avoided by always using the unsigned u when the constant is intended for unsigned operations.
        #define CONST_UNSIGNED 127u
        #define CONST_ALSO_UNSIGNED 127u  // <-- Added "u", now no warning
        uint8_t unsigned_var = (CONST_UNSIGNED + CONST_ALSO_UNSIGNED);
      

Chars and vararg functions

Parameters (chars, ints, etc) to printf / sprintf should always be explicitly cast to avoid type related parameter passing issues.

For example, below will result in the likely unintended output:

sprintf(str_temp, "%u, %d, %x\n", UINT16_MAX, INT16_MIN, UINT16_MAX);
printf("%s",str_temp);
// Will output: "65535, 0, 8000"

Instead this will give the intended output:

printf("%s",str_temp);
// Will output: "65535, -32768, FFFF"

Chars

In standard C when chars are passed to a function with variadic arguments (varargs, those declared with ... as a parameter), such as printf(), those chars get automatically promoted to ints. For an 8 bit CPU such as the Game Boy's, this is not as efficient or desirable in most cases. So the default SDCC behavior, which GBDK-2020 expects, is that chars will remain chars and not get promoted to ints when explicitly cast as chars while calling a varargs function.

For example:

unsigned char i = 0x5A;
// NO:
// The char will get promoted to an int, producing incorrect printf output
// The output will be: 5A 00
printf("%hx %hx", i, i);
// YES:
// The char will remain a char and printf output will be as expected
// The output will be: 5A 5A
printf("%hx %hx", (unsigned char)i, (unsigned char)i);

Some functions that accept varargs:

Also See:

When C isn't fast enough

Todo:
Update and verify this section for the modernized SDCC and toolchain

For many applications C is fast enough but in intensive functions are sometimes better written in assembly. This section deals with interfacing your core C program with fast assembly sub routines.

Calling convention

SDCC in common with almost all C compilers prepends a _ to any function names. For example the function printf(...) begins at the label _printf::. Note that all functions are declared global.

Functions can be marked with OLDCALL which will cause them to use the __sdcccall(0) calling convention (the format used prior to in SDCC 4.2 & GBDK-2020 4.1.0).

Starting with SDCC 4.2 and GBDK-2020 4.1.0 the new default calling convention is__sdcccall(1).

For details about the calling convetions, see sections SM83 calling conventions and Z80, Z180 and Z80N calling conventions in the SDCC manual.

Variables and registers

Getting at C variables is slightly tricky due to how local variables are allocated on the stack. However you shouldn't be using the local variables of a calling function in any case. Global variables can be accessed by name by adding an underscore.

Segments / Areas

The use of segments/areas for code, data and variables is more noticeable in assembler. GBDK and SDCC define a number of default ones. The order they are linked is determined by crt0.s and is currently as follows for the Game Boy and related clones.

  • ROM (in this order)
    • _HEADER: For the Game Boy header
    • _CODE: CODE is specified as after BASE, but is placed before it due to how the linker works.
    • _HOME
    • _BASE
    • _CODE_0
    • _INITIALIZER: Constant data used to init RAM data
    • _LIT
    • _GSINIT: Code used to init RAM data
    • _GSFINAL
  • Banked ROM
    • _CODE_x Places code in ROM other than Bank 0, where x is the 16kB bank number.
  • WRAM (in this order)
    • _DATA: Uninitialized RAM data
    • _BSS
    • _INITIALIZED: Initialized RAM data
    • _HEAP: placed after _INITIALIZED so that all spare memory is available for the malloc routines.
    • STACK: at the end of WRAM
INT16_MIN
#define INT16_MIN
Definition: stdint.h:117
UINT16_MAX
#define UINT16_MAX
Definition: stdint.h:133
uint16_t
unsigned short int uint16_t
Definition: stdint.h:52
int16_t
short int int16_t
Definition: stdint.h:44
printf
void printf(const char *format,...) OLDCALL REENTRANT
sprintf
void sprintf(char *str, const char *format,...) OLDCALL REENTRANT