This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
i386.h misstype?
- From: "Alexander Aganichev" <aaganichev at yandex dot ru>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 7 May 2003 11:51:51 +0400 (MSD)
- Subject: i386.h misstype?
- Reply-to: aaganichev at yandex dot ru
Hi!
I browsed the gcc 3.2.3 code and I think that I find misstype in i386.h. I'm not familiar with the internals of gcc, so I don't know if this is an error. I'm just hoping someone who familiar with internals can spend few minutes to look on this and deside whether it bug or not. Here is proposed change:
*** i386.orig Mon May 5 23:19:16 2003
--- i386.h Wed May 7 11:39:01 2003
***************
*** 1059,1075 ****
#define MODES_TIEABLE_P(MODE1, MODE2) \
((MODE1) == (MODE2) \
|| (((MODE1) == HImode || (MODE1) == SImode \
|| ((MODE1) == QImode \
&& (TARGET_64BIT || !TARGET_PARTIAL_REG_STALL)) \
|| ((MODE1) == DImode && TARGET_64BIT)) \
&& ((MODE2) == HImode || (MODE2) == SImode \
! || ((MODE1) == QImode \
&& (TARGET_64BIT || !TARGET_PARTIAL_REG_STALL)) \
|| ((MODE2) == DImode && TARGET_64BIT))))
/* Specify the modes required to caller save a given hard regno.
We do this on i386 to prevent flags from being saved at all.
Kill any attempts to combine saving of modes. */
--- 1059,1075 ----
#define MODES_TIEABLE_P(MODE1, MODE2) \
((MODE1) == (MODE2) \
|| (((MODE1) == HImode || (MODE1) == SImode \
|| ((MODE1) == QImode \
&& (TARGET_64BIT || !TARGET_PARTIAL_REG_STALL)) \
|| ((MODE1) == DImode && TARGET_64BIT)) \
&& ((MODE2) == HImode || (MODE2) == SImode \
! || ((MODE2) == QImode \
&& (TARGET_64BIT || !TARGET_PARTIAL_REG_STALL)) \
|| ((MODE2) == DImode && TARGET_64BIT))))
/* Specify the modes required to caller save a given hard regno.
We do this on i386 to prevent flags from being saved at all.
Kill any attempts to combine saving of modes. */
--
Alexander Aganichev
url: http://aaganichev.narod.ru
e-mail: aaganichev@yandex.ru
gsm: +7-095-786-1339