|
From: | Laurent Amon |
Subject: | Re: [Qemu-devel] /* XXX: suppress this hack */ |
Date: | Sun, 31 Oct 2004 15:35:34 +0100 |
On 31 oct. 04, at 13:40, Magnus Damm wrote:
I use the stock gcc in the developer tools, provided by Apple. I don't use -faltivec since it enables Altivec code if you use it but do not generate Altivec code from regular code (as of gcc 3.3).Huh. Just curious, this "regular" gcc 3.3, is it from FSF or is it a Darwin-version? Do you use "-faltivec" or "-maltivec -mabi=altivec" to add altivec support? The latter is FSF. This is what I use right now (FSF): address@hidden damm $ gcc --versiongcc (GCC) 3.4.1 20040803 (Gentoo Linux 3.4.1-r3, ssp-3.4-2, pie-8.7.6.5)Copyright (C) 2004 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
% gcc --version gcc (GCC) 3.3 20030304 (Apple Computer, Inc. build 1495) Copyright (C) 2002 Free Software Foundation, Inc.This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
My CFLAGS for compiling qemu are :CFLAGS=-Wall -O2 -fkeep-inline-functions -finline-functions -fno-strict-aliasing -mpowerpc-gpopt -mpowerpc-gfxopt -mcpu=7400
but it seems that only the -mcpu=7400 makes a difference. It may be that gcc 3.4.1 optimizes better.
I don't have much time for testing right now (on vacation next week and lots to do before that), but I'll do it if I find some time.
Lga.
[Prev in Thread] | Current Thread | [Next in Thread] |