iris/kaizen
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
00cc9309cb3a9e41afe5def8dcb9bf5b089b9a21
kaizen/external/SDL/docs/README-versions.md
T
iris 00cc9309cb Squashed 'external/ircolib/' changes from ce3cd726c..de6e324bd 
de6e324bd separate emu thread
10d3daf86 Roms List improvements
95d202f37 Let's make the rom list process on a separate thread so the emulator doesnt take ages to load.
fc306967f Wow the ROM Header was just completely busted. Game list view works now
bad1691ee fuck this shit
2b59e5f46 game list in progress
d26417b83 remappable inputs in progress
ac4af8106 input
e72abc240 update readme
430139dc9 Qt6 frontend
3080d4d45 Fix this small bug too
08cd13b85 Cop0 unused functions do not actually pose a threat (as per manual). They don't do anything, so shall we.
61bb4fb44 make idle loop detection a little more specific with where the load goes
b037de4c3 SAZDFsdff
12e81e73e need to figure out why n64-systemtest loops indefinitely at some address that appears to be valid (i think it's me not invalidating the cache properly)
204f0e13b idle skipping seems to work!
cb8bb634a sdkfjlasdf
58e5c89c1 Fix compilation issue on my machine (no idea)
24fb2898e attempting more serious idle skipping
214719577 Place rsp.Step inside cached interpreter. Gains about 3 more fps
bb97dcc23 mmmmm
920b77d38 wjkhasdfjhkasdf
430ccdab4 it's a start...
4f42a673a Cached interpreter plays Mario 64. Start looking into RSP as well
c9a030787 idle skipping works!
5fbda03ce new idea
366637aba Idle skipping... maybe?
609fa2fb0 Cache instructions implemented but broken lmao. Commented out for now
e140a6d12 - Stop using inheritance for CPU, instead use composition. - Introduce KAIZEN_JIT_ENABLED optional define instead of relying on __aarch64__ and the like. - More cache work
68e613057 prep cache impl
811b4d809 fix clang format
fda755f7d idk
d5024ebbf small MI refactor in preparation of (eventually) implementing the RDRAM interface properly
694b45341 Merge commit '206dcdedf195fb320913584180edb12c7731e396' as 'external/SDL'
206dcdedf Squashed 'external/SDL/' content from commit 4d17b99d0a
4d16e1cb4 need to update sdl
848b19920 Fix compilation error
db61b5299 Merge commit 'e94a94559f28e49678fbcf72199a5258137b0fe9' as 'external/imgui'
e94a94559 Squashed 'external/imgui/' content from commit 02e9b8cac
52edb3757 need to update imgui
c1a705e86 Emulate weird JALR behaviour
4b4c32f4b Fix exception for "unusable COP1" in 4 instructions i missed accidentally (again)
df5828142 Bug putting 0s in the log everywhere
f8b580048 Make isviewer a sink to file
8241e9735 Fix exception for "unusable COP1" in 4 instructions i missed accidentally
b29715f20 small changes
d9a620bc1 make use of my new small utility library
0d1aa938e Add 'external/ircolib/' from commit 'ce3cd726c8df8388d554abf8bb55d55020eb4450'
e64eb40b3 Fuck git

git-subtree-dir: external/ircolib
git-subtree-split: de6e324bde
2026-06-15 11:56:38 +02:00

2.4 KiB
Raw Blame History

Versioning

Since 3.2.0

SDL follows an "odd/even" versioning policy, similar to GLib, GTK, Flatpak and older versions of the Linux kernel:

  • If the minor version (second part) and the patch version (third part) is divisible by 2 (for example 3.2.6, 3.4.0), this indicates a version of SDL that is believed to be stable and suitable for production use.

    • In stable releases, the patchlevel or micro version (third part) indicates bugfix releases. Bugfix releases may add small changes to the ABI, so newer patch versions are backwards-compatible but not fully forwards-compatible. For example, programs built against SDL 3.2.0 should work fine with SDL 3.2.8, but programs built against SDL 3.2.8 may not work with 3.2.0.

    • The minor version increases when significant changes are made that require longer development or testing time, e.g. major new functionality, or revamping support for a platform. Newer minor versions are backwards-compatible, but not fully forwards-compatible. For example, programs built against SDL 3.2.x should work fine with SDL 3.4.x, but programs built against SDL 3.4.x may not work with 3.2.x.

  • If the minor version (second part) or patch version (third part) is not divisible by 2 (for example 3.2.9, 3.3.x), this indicates a development prerelease of SDL that is not suitable for stable software distributions. Use with caution.

    • The patchlevel or micro version (third part) increases with each prerelease.

    • Prereleases are backwards-compatible with older stable branches. For example, programs built against SDL 3.2.x should work fine with SDL 3.3.x, but programs built against SDL 3.3.x may not work with 3.2.x.

    • Prereleases are not guaranteed to be backwards-compatible with each other. For example, new API or ABI added in 3.3.0 might be removed or changed in 3.3.1. If this would be a problem for you, please do not use prereleases.

    • Only use a prerelease if you can guarantee that you will promptly upgrade to the stable release that follows it. For example, do not use 3.3.x unless you will be able to upgrade to 3.4.0 when it becomes available.

    • Software distributions that have a freeze policy (in particular Linux distributions with a release cycle, such as Debian and Fedora) should only package stable releases, and not prereleases.

Reference in New Issue View Git Blame Copy Permalink