stdarch VS blog_os

Good to know! How would you compare it with the std_detect implementation, underlying the standard library (https://github.com/rust-lang/stdarch/tree/master/crates/std_detect)?

Fortunately, @burntsushi (thanks) is sharing the workaround in the rust-lang github issue. The trick is to reinterpret a (non-tagged) union for this.

The stdarch tests will test target-specific stuff like SIMD while to UI tests are more generic. They both test that the compiler will produce an executable that produce the correct output (or that rustc itself will produce the correct output).

I made enough progress to be able to compile the tests of stdarch and most of them pass: that's a huge milestone!

You can check the code. Apparently the std implementation uses the OSXSAVE register to check that the OS supports saving AVX/AVX2 registers during context switches and only then enables it. In a non-std context one might not generally be able to depend on the OSXSAVE register.

but it seems to be flawed because even the example: https://github.com/phil-opp/blog_os/tree/post-02

I suggest looking at the 3rd edition of Philipp Oppermann's blog OS that I mentioned. It's still very much a work-in-progress, but the section on UEFI booting is pretty much done. It's not hosted anywhere yet, so you'll have to clone the repo and switch to the edition-3 branch, then install Zola 0.13 (cargo install zola --git https://github.com/getzola/zola.git --tag v0.13.0) and run zola serve in the blog directory.

RedoxOS, an OS written in Rust A tutorial on making an OS in Rust, complwte with bootable source

I'm currently working on a tutorial for (1). It's still in a very early stage, but maybe it helps you to get started: https://github.com/phil-opp/blog_os/blob/edition-3/blog/content/edition-3/posts/02-booting/uefi.md