qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Leonardo E. Reiter" <lreiter@win4lin.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Compile errors on Solaris for qemu 0.8.2
Date: Mon, 24 Jul 2006 09:37:34 -0400	[thread overview]
Message-ID: <44C4CD1E.1020706@win4lin.com> (raw)
In-Reply-To: <db7b3ca90607240623s55632cc0pb55074502fee9f92@mail.gmail.com>

I ran into this myself yesterday.  I couldn't figure out a definitive
answer, because I am no expert on the SPARC architecture, but it appears
that at least on an UltraSparc IIi machine from a few years ago, the
"sparc V9" instructions are supported.  However, the gcc by default
doesn't define __sparc_v9__ on that architecture.  There are some -m
flags that can be passed to gcc (like multisparc, etc.), but I'm not
sure for what host machines they are appropriate exactly.  Perhaps the
SPARC experts on the list can comment more, but in the meantime, the
following simple (but likely incorrect) patch worked fine for me:

Index: cpu-all.h
===================================================================
RCS file: /cvsroot/qemu/qemu/cpu-all.h,v
retrieving revision 1.57
diff -a -u -r1.57 cpu-all.h
--- cpu-all.h   18 Jul 2006 21:23:34 -0000      1.57
+++ cpu-all.h   24 Jul 2006 13:35:47 -0000
@@ -971,7 +971,7 @@
     return val;
 }

-#elif defined(__sparc_v9__)
+#elif defined(__sparc__)

 static inline int64_t cpu_get_real_ticks (void)
 {


Regards,

Leo Reiter

Jonathan Kalbfeld wrote:
> At airport so can't paste.  cpu_get_real_ticks doesn't resolve in
> vl.o.  Using blastwave gcc 3.4.6.  What am I missing?

-- 
Leonardo E. Reiter
Vice President of Product Development, CTO

Win4Lin, Inc.
Virtual Computing that means Business
Main: +1 512 339 7979
Fax: +1 512 532 6501
http://www.win4lin.com

  reply	other threads:[~2006-07-24 13:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-24 13:23 [Qemu-devel] Compile errors on Solaris for qemu 0.8.2 Jonathan Kalbfeld
2006-07-24 13:37 ` Leonardo E. Reiter [this message]
2006-07-24 15:28   ` Jonathan Kalbfeld
2006-07-24 16:35   ` Blue Swirl
2006-07-25 12:02     ` Jonathan Kalbfeld

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=44C4CD1E.1020706@win4lin.com \
    --to=lreiter@win4lin.com \
    --cc=qemu-devel@nongnu.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: link
Be 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 NNTP newsgroup(s).