This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[patch] m68k.h: Change PREFERRED_STACK_BOUNDARY for fido.
- From: Kazu Hirata <kazu at codesourcery dot com>
- To: gcc-patches at gcc dot gnu dot org
- Cc: law at redhat dot com, schwab at suse dot de
- Date: Sun, 15 Apr 2007 06:49:16 -0700
- Subject: [patch] m68k.h: Change PREFERRED_STACK_BOUNDARY for fido.
Hi,
Attached is a patch to change PREFERRED_STACK_BOUNDARY for fido as
Unaligned access has performance penalty on fido.
Tested on fido-none-elf. OK to apply?
Kazu Hirata
gcc/
2007-04-15 Kazu Hirata <kazu@codesourcery.com>
* config/m68k/m68k.h (PREFERRED_STACK_BOUNDARY): Prefer 32-bit
alignment on fido.
Index: gcc/config/m68k/m68k.h
===================================================================
--- gcc/config/m68k/m68k.h (revision 123811)
+++ gcc/config/m68k/m68k.h (working copy)
@@ -289,8 +289,9 @@ Boston, MA 02110-1301, USA. */
#define STACK_BOUNDARY 16
#define FUNCTION_BOUNDARY 16
#define EMPTY_FIELD_BOUNDARY 16
-/* ColdFire strongly prefers a 32-bit aligned stack. */
-#define PREFERRED_STACK_BOUNDARY (TARGET_COLDFIRE ? 32 : 16)
+/* ColdFire and fido strongly prefers a 32-bit aligned stack. */
+#define PREFERRED_STACK_BOUNDARY \
+ ((TARGET_COLDFIRE || TARGET_FIDOA) ? 32 : 16)
/* No data type wants to be aligned rounder than this.
Most published ABIs say that ints should be aligned on 16-bit