PVB/lemur
PVB
/
lemur
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 36 Wiki Activity

Update Profiling with Lemur

Simon Gellis 2025-09-02 04:38:45 +00:00
parent 4a48dac9bd
commit 8dc4c27d7d
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Profiling-with-Lemur.md

@ -10,6 +10,8 @@ To give you the most insight into your code, Lemur reads all information it can
* **Better: ELF file** (`.elf` extension, possibly no extension): the profile will include function names. This is much easier to read, but won't tell you as much as...
* **Best: ELF file with debug info**: the profile will include inlined functions as well. This gives you the most information possible.
Note: the current version of VUEngine Studio deletes ELF files after builds unless you modify the makefile. The next VUEngine Studio version will (probably) not do this.
### Compiling with debug info
To get the most useful profiles, your game's `.elf` file should include debug info. To do this, simply add `-g` to your `CFLAGS`.
@ -18,7 +20,7 @@ The `-g` flag is supported in
* [v810-gcc](https://github.com/jbrandwood/v810-gcc) v4.9.4
* [v810-llvm](https://github.com/SupernaviX/v810-llvm/releases)
Note that VUEngine Studio uses an older version of v810-gcc, so source-level debugging doesn't work for VUEngine games. This will be fixed Eventually™️.
Note that VUEngine Studio uses an older version of v810-gcc, so inlined functions won't appear in profiles for VUEngine games. This will be fixed Eventually™️.
This debug info will be added to your game's `.elf` file, but stripped from the final `.vb` file. This means compiling with `-g` won't make your ROM bigger or slower.