Right, so either Intels CPUID manual is fucking stupid or my qemu CPU has brain cancer in it's fucking silicon head.

x80000004 contains not ascii stuff but x8000003 and x80000002 fucking do.

I'm stranded with two thirds of a CPU brand string.
Fuck

Brain cancer. Last time I worked on a project that involved writing the bootloader for a cpu (custom hardware, real time without an OS), my main memory was "this is what the spec says, this is what actually happens, let's just implement the spec and reverse engineer the differences".

Wouldn't be surprised if the documentation is wrong. They have 3000 pages to get it right and yet they all suck ass

Are you using __get_cpuid?

Found some info that you should use __get_cpuid__count instead. It inits ecx as well as eax.

https://stackoverflow.com/questions...

https://github.com/gcc-mirror/gcc/...

https://sandpile.org/x86/cpuid.htm/...

Took me a bit to get my head around this.

@Demolishun nah I'm using my own Implementation.
But I've managed to somehow fix it.

@Ranchonyx "I've managed to somehow fix it."

Or it could be a heisenbug.

In other words you recompiled and the problem magically went away, right?

@Wisecrack not quite. But similar.