This is the mail archive of the 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]

GCC compat testsuite

Hello Janis,

For various reasons it might be useful to run the compat testsuite against a 
non-GCC compiler (for example, the vendor compiler might help to correctly 
implement an awkward ABI like the SPARC64's).  Now some testcases use 
GCC-specific idioms, so they don't compile with non-GCC compilers, although 
they contain individual tests that would.

I've attached a logfile for a GCC vs Sun Studio 8 CC run on SPARC64:
- _Complex means the keyword is used with non-fp types,
- packed means the 'packed' attribute is used,
- __INT_MAX__ means '__INT_MAX__' is tested,
- array[0] means an array is declared with a null size,
- ?? means the cause is unknown (most likely a deviation from the ABI).

What about clearly separating the testcases that use only Standard C99 
features from the GCC-specific ones? The latter could be prefixed by "gcc_".

I'm ok to do the work (btw, is it really necessary to test zero-sized 

I've also attached a tiny patch that fixes the FAIL marked as 'abort()'.

2004-01-05  Eric Botcazou  <>

	* gcc.dg/compat/sdata-section.h: Declare 'abort'.

Eric Botcazou
Index: gcc.dg/compat/sdata-section.h
RCS file: /cvs/gcc/gcc/gcc/testsuite/gcc.dg/compat/sdata-section.h,v
retrieving revision 1.1
diff -u -r1.1 sdata-section.h
--- gcc.dg/compat/sdata-section.h	8 Jul 2003 17:36:00 -0000	1.1
+++ gcc.dg/compat/sdata-section.h	5 Jan 2004 16:40:17 -0000
@@ -3,3 +3,5 @@
+extern void abort (void);

Attachment: gcc_vs_cc-failed.txt
Description: Text document

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