[] > As I explained several times, this problem must be fixed > on both sides - both gmp and qemu, and it is "more correct" > to fix it in gmp side. The problem im gmp is that it uses > "abort()" statements in cases where it detects "impossible", > to its "thinking", CPU. Instead of these aborts(), it should > just use whatever default optimization modes it already uses > for these "default" cases. Ie, just changing "abort()" into > "break" in the mentioned code in gmp is enough to fix it on > gmp side. > > For qemu side, I don't want to make a Debian-specific change > for this. If upstream decides to change default CPU type, > Debian will inherit that change, and I'll happily backport it > to the Debian package if that happens in some later upstream > release. This is exactly why I started that discussion on > qemu-devel list.
One additional note. I think I can manage a patch that will use kvm64 cpu type in case -enable-kvm is specified, and qemu64 if not. It will differ from upstream, which I dislike, but it should fix at least the current issue. ..Which is, indeed, can be trivially fixed "externally" by invoking qemu with the right options, explicitly specifying required CPU type and other machine details. That to say: this bugreport is only about default value of an option (-cpu), which has this value since the day one. Thanks, /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
