This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [patch] tuning gcc for AMDFAM10 processor (patch 2)

From: "Uros Bizjak" <ubizjak at gmail dot com>
To: "GCC Patches" <gcc-patches at gcc dot gnu dot org>
Cc: "Jagasia, Harsha" <harsha dot jagasia at amd dot com>
Date: Tue, 30 Jan 2007 10:29:02 +0100
Subject: Re: [patch] tuning gcc for AMDFAM10 processor (patch 2)

Hello!

This is the 2nd of 11 patches to tune gcc for AMD's AMDFAM10 processor
(based on mainline rev 121295). This patch defines mtune=amdfam10 and
enables/disables some existing tuning choices for amdfam10 such as
aligning loop tops to 32 bytes and using push/pops instead of moves for
prologue/epilogue.

 #define m_GENERIC64 (1<<PROCESSOR_GENERIC64)
 #define m_GENERIC (m_GENERIC32 | m_GENERIC64)
+#define m_ATHLON_K8_AMDFAM10  (m_K8 | m_ATHLON | m_AMDFAM10)

This part isn't described in ChangeLog.

        (x86_use_leave, x86_push_memory, int x86_movx, x86_unroll_strlen,
        x86_cmove, x86_fisttp, x86_3dnow_a, x86_deep_branch,
        x86_use_simode_fiop, x86_promote_QImode,

x86_fisttp is gone.

BTW: Is there really a reason to use combined defines , such as
m_ATHLON_K8_AMDFAM10? These are used only in i386.c in a lines below
and IMO don't bring us anything.

Uros.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]