asm_book VS libnx

Looks useful for a beginner to asm in general, but for someone like me who've been coding asm for other processors for decades it might a bit too basic.

I have been using this other "tutorial" for AArch64 assembly, which I think might be more useful for someone coming from asm on another processor: https://github.com/pkivolowitz/asm_book

This will make it into the assembly language book located here.

A new chapter on how to implement jump or branch tables has been added to the book available here. The examples also give insight into how some optimized switch statements are implemented (but not all switch statements).

One resource: https://github.com/pkivolowitz/asm_book. Good luck to you in your endeavors.

The book located here on GitHub has had many additions since an announcement was last made here.

I'm wondering about the loss of the marking due to thread switching... if the line were truly lost, the code found here wouldn't work... but it does. The example code presents a hidden update problem with solution by C++ atomic and with hand coded atomics.

This is a video in which a trivial C program (print 0 to 9 using printf) is written for AARCH64 ARM Linux and then modified for the convergence macros written for this book on AARCH64 assembly language programming.

Here is a link to the first chapter that successively breaks down a simple program from C++ down into C and then down into assembly language. Towards the bottom, the same program is presented using the convergence macros.

The SDK used by most, if not all switch developers, is libnx. As a Rust enthusiast, I wanted the core logic in Rust so I just built the display in C/C++ which the switch library is written in.

Could you publish all of the source code that you wrote, but leave out Unity source code and plugin source code, while also linking to where people can get the proprietary engine/plugins? That way, when someone eventually makes a Unity-compatible engine, someone could re-implement all the plugins and release a full source version. I think this is what rRootage Reloaded did, publishing the code of the game logic but not any Nintendo SDK stuff (A libre replacement Switch SDK exists (libnx, I think), and I've considered modifying rRoortage Reloaded to work with that, but I haven't gotten around to it (plus I don't really know what I'm doing lol).).

If somebody interested in homebrew development for Nintendo Switch - take a look at libnx and switchbrew wiki

https://github.com/switchbrew/libnx (SDK for writing homebrew applications)

If you need a proof: https://github.com/switchbrew/libnx/issues/161#issuecomment-473910049