I’m not sure I completely understand the question.

But vendor / custom UEFI implementations could obviously pass around whatever structures they want.

The EFI RUNTIME services - for example - could expose custom functions in a proprietary UEFI implementation. Though in my experience this usually is not the case.

Grub should run as an EFI bootloader binary after core UEFI is done. Afaik there is no particular ring / exception level required here. It could vary depending on UEFI implantation.

on android arm32/64 devices I obviously don’t see grub, but core EFI handles and services are not modified much. If anything it’s just expanded to support the next bootloader stage and handle stuff like key combos to select next boot image

I feel that.

I still favor gcc over clang

Lol.

This is barbaric and I love it.

I thought I was going to hate this as another useless tool.

And while that’s still mostly true - I do see the vision here. And the clean c code and man page docs makes this a win for me.

Simple utility that does what it says. I also like the single char status output.

Til. Thanks for sharing this

I develop mostly in C and largely for creating shellcode.

I have run into very weird issues with clang relocating code and data segments even when using a custom linker script

Def curl and wget!

Zsh is great but I ended up falling back to bash for simplicity.