public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mikpelinux at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/61570] -march=native CPU you selected does not support x86-64 instruction under QEMU Date: Fri, 20 Jun 2014 10:13:00 -0000 [thread overview] Message-ID: <bug-61570-4-NE7MerEbFD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61570-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61570 Mikael Pettersson <mikpelinux at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mikpelinux at gmail dot com --- Comment #3 from Mikael Pettersson <mikpelinux at gmail dot com> --- (In reply to Jakub Jelinek from comment #2) > Sure, but for this model AFAIK we go through the default: case of PENTIUMPRO > anyway, where we only test the flags, so even if it used some completely > unknown family number, it would still behave the same. > So, can't we before: > else if (has_sse3) > /* It is Core Duo. */ > cpu = "pentium-m"; > else if (has_sse2) > /* It is Pentium M. */ > cpu = "pentium-m"; > just add > else if (has_longmode) > /* Some unknown 64-bit CPU, perhaps emulator? */ > cpu = "x86-64"; > ? That looks reasonable. > Otherwise, QEMU, if it doesn't want to support SSSE3 and SSE3, and doesn't > want to support 3dNOW either would need to identify itself as something > other than Intel and AMD. I don't recall if the 1st gen 64-bit Netburst had SSE3/SSSE3 or not, but if it didn't then emulating that should be close enough to generic x86_64. Otherwise I'd prefer qemu to choose a unique vendor, unique family, or some high unused model (e.g. all-bits-one).
next prev parent reply other threads:[~2014-06-20 10:13 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-06-20 7:15 [Bug target/61570] New: " jakub at gcc dot gnu.org 2014-06-20 9:37 ` [Bug target/61570] " jakub at gcc dot gnu.org 2014-06-20 10:13 ` mikpelinux at gmail dot com [this message] 2014-06-23 16:29 ` hjl at gcc dot gnu.org 2014-06-24 14:46 ` hjl at gcc dot gnu.org 2014-06-24 14:58 ` jakub at gcc dot gnu.org 2014-06-24 15:07 ` jakub at gcc dot gnu.org 2014-06-24 15:14 ` jakub at gcc dot gnu.org 2014-11-15 16:45 ` fxcoudert at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-61570-4-NE7MerEbFD@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).