All of lore.kernel.org
 help / color / mirror / Atom feed
* [Qemu-devel] Re: compile qemu for a G5
       [not found] <200410110346.7d6416a3a5f2f@rly-yi05.mx.aol.com>
@ 2004-10-11 13:32 ` Fred Hope
  2004-10-11 15:36   ` André Braga
  0 siblings, 1 reply; 3+ messages in thread
From: Fred Hope @ 2004-10-11 13:32 UTC (permalink / raw)
  To: qemu-devel

So for my iMac G5 1.8 GHz it would be -mcpu=970 or what?  The only 
thing I know about the G5 is that it is really the PowerPC 970.  Also, 
I use this flag when I run ./configure, right?  Not the "make" command 
itself?

Thanks,
Fred Hope

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [Qemu-devel] Re: compile qemu for a G5
  2004-10-11 13:32 ` [Qemu-devel] Re: compile qemu for a G5 Fred Hope
@ 2004-10-11 15:36   ` André Braga
  0 siblings, 0 replies; 3+ messages in thread
From: André Braga @ 2004-10-11 15:36 UTC (permalink / raw)
  To: qemu-devel

On Mon, 11 Oct 2004 06:32:44 -0700, Fred Hope <fredakbar@aol.com> wrote:
> So for my iMac G5 1.8 GHz it would be -mcpu=970 or what?  The only
> thing I know about the G5 is that it is really the PowerPC 970.  Also,
> I use this flag when I run ./configure, right?  Not the "make" command
> itself?

-mcpu=power4 is the correct flag. As of January there was a bug in GCC
regarding this flag and 64-bit code, so I suggest looking for updates
if your xcode tools happen to be somewhat old.

Other than that, G5 behaves better if code is aligned to 32 byte
boundaries, because of the longer cache lines. Those flags may help:
-falign-functions=32, -falign-labels=32, -falign-loops=32,
-falign-jumps=32. They will potentially make the executable fairly
large, though, which may or may not be a problem for you.

Also take a look at these pages and their links:
http://developer.apple.com/technotes/tn/tn2087.html
http://developer.apple.com/performance/g5optimization.html

Back in June there were some issues with the configure file flags
being completely ignored by some makefiles, and I sent a patch to the
list, but I don't know if they were applied (haven't been able to work
with the sources since then), so I suggest looking at the makefiles
for places where those flags should appear but end up not showing at
all.


cheers,
A.




-- 
"A year spent in artificial intelligence is enough to make one believe in God"
Alan J. Perlis

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Qemu-devel] Re: compile qemu for a G5
       [not found] <200410111157.4cf416aad54109@rly-xi03.mx.aol.com>
@ 2004-10-12  2:43 ` Fred Hope
  0 siblings, 0 replies; 3+ messages in thread
From: Fred Hope @ 2004-10-12  2:43 UTC (permalink / raw)
  To: qemu-devel

Well, now I can't download the source from CVS...I've tried both cvs up 
and cvs checkout, and I get this:

nongnu.org: Operation timed out
cvs [update aborted]: end of file from server (consult above messages 
if any)

Is anyone else having trouble getting the source?  I could always use 
the 0.6.0 source but that's kind of old, I'd rather have the latest 
code.

Fred Hope

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2004-10-12  2:51 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <200410110346.7d6416a3a5f2f@rly-yi05.mx.aol.com>
2004-10-11 13:32 ` [Qemu-devel] Re: compile qemu for a G5 Fred Hope
2004-10-11 15:36   ` André Braga
     [not found] <200410111157.4cf416aad54109@rly-xi03.mx.aol.com>
2004-10-12  2:43 ` Fred Hope

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.