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: XFAILing gcc.dg/uninit-C.c on non 64-bit platforms?

From: Jim Wilson <wilson at tuliptree dot org>
To: Roger Sayle <roger at eyesopen dot com>
Cc: Kaveh Ghazi <ghazi at caip dot rutgers dot edu>, gcc-patches at gcc dot gnu dot org
Date: Thu, 05 Jun 2003 11:56:52 -0700
Subject: Re: XFAILing gcc.dg/uninit-C.c on non 64-bit platforms?
References: <Pine.LNX.4.44.0305282111430.2053-100000@www.eyesopen.com>

Roger Sayle wrote:

The question is therefore what is the correct way to limit this
test to platforms that support __attribute__ ((mode (TI))?

There is an easy way that is almost completely correct. Add ifdefs for __LP64__. This is defined for all 64-bit targets with 64-bit longs and pointers. As far as I know, that is all of the current 64-bit targets. However, 64-bit windows is P64, so it wouldn't work there, but we don't have support for this target yet.

TImode exists if HOST_BITS_PER_WIDE_INT is 64 or more. That would be the correct test. There is no way to test for this in the testsuite without adding a new builtin macro, and it seems silly to add one just for a single testcase in the testsuite.

Jim

Follow-Ups:
- Re: XFAILing gcc.dg/uninit-C.c on non 64-bit platforms?
  - From: Kaveh R. Ghazi

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