Of course it’s open source, I get that. When I say „xyz should be done“
then in the sense of „2+2 should be 4“ not in the sense of „you must
implement xyz right now“ ;)
Nonetheless, if you run e.g. on an ARM platform the command
qemu-system-x86_64 -cpu help
then it shouldn’t list a slew of CPUs
BTW: just because I bracket a report with why I think a matter is worth
fixing, shouldn’t make it „invalid“.
The instructions aren’t implemented, yet the CPUs are listed as
available, which is a bug in my book, as functionality is advertised
that is unavailable.
--
You received this bug notifica
The comments with the other reports were just in support of getting them
fixed, and providing a reason as to why that matters. Someone looking at
those reports may not read this one, and as the issues are symptoms of
the same larger issue, this report was filed as an overarching report,
as AVX is j
Public bug reported:
It seems that QEMU has stopped emphasizing the EMU part of the name, and
is too much focused on virtualization.
My interest is at running legacy operating systems, and as such, they must run
on foreign CPU platforms. m68 on intel, intel on ARM, etc.
Time doesn't stand still,
If I may be so free:
It seems that QEMU has stopped emphasizing the EMU part of the name, and
is too much focused on virtualization.
My interest is at running legacy operating systems, and as such, they must run
on foreign CPU platforms. m68 on intel, intel on ARM, etc.
Time doesn't stand still,
If I may be so free:
It seems that QEMU has stopped emphasizing the EMU part of the name, and
is too much focused on virtualization.
My interest is at running legacy operating systems, and as such, they must run
on foreign CPU platforms. m68 on intel, intel on ARM, etc.
Time doesn't stand still,
