Compiler issue...

Jason Baker jbaker at
Tue Jan 26 14:33:32 PST 1999

> Actually, I would suggest hiding the [0] arrays behind a macro called
> ALIGNMENT(), as this would hide the GNU-ism and make it easier to fix
> under other compilers (which might provide pragmas or somesuch for
> defining the alignment of a structure).

Can you put a pragma inside a macro?  I didn't think you could put a
#include inside a macro.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         From kaffe-owner at  Wed Jan 27 10:45:05 1999
Received: (from majordom at localhost)
	by (8.8.7/8.8.7) id KAA00651
	for kaffe-list; Wed, 27 Jan 1999 10:45:05 -0500
Resent-Date: Wed, 27 Jan 1999 10:45:05 -0500
Resent-Message-Id: <199901271545.KAA00651 at>
Received: from ( [])
	by (8.8.7/8.8.7) with ESMTP id KAA00637
	for <kaffe at>; Wed, 27 Jan 1999 10:44:54 -0500
Received: from localhost (proski at localhost)
	by (8.8.7/8.8.7) with ESMTP id SAA03583
	for <kaffe at>; Wed, 27 Jan 1999 18:44:13 +0300
X-Authentication-Warning: proski owned process doing -bs
Date: Wed, 27 Jan 1999 18:44:12 +0300 (EET)
From: Pavel Roskin <pavel_roskin at>
X-Sender: pavel_roskin at
To: kaffe at
Subject: Re: Compiler issue...
In-Reply-To: <36AE0BD2.11335E4D at>
Message-ID: <Pine.LNX.4.05.9901271818480.3508-100000 at>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-kaffe at
Precedence: bulk
Reply-To: kaffe at
Errors-To: kaffe-error at
X-loop: kaffe at
X-mailing-list: kaffe at
Resent-from: kaffe at


> Perhaps it is worth considering gcc -ansi -pedantic as the standard
> command line options for gcc. Some of these problems would be minimized.

I would prefer
$(CC) -D_GNU_SOURCE -ansi -pedantic

Please note, that glibc doesn't declare some symbols when _GNU_SOURCE is
not declared, which is the case when -ansi option is given to gcc.
I know several projects which suffer from such "pedantism", notably PAM
(pluggable authentication modules), which contains dozens of __USE_BSD,
__POSIX_SOURCE and even "#include <features.h>" in random places.

IMHO, Kaffe may and should use available features and extensions, even not
described in the ANSI and ISO standards.

Pavel Roskin.

More information about the kaffe mailing list