This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: patch for problem with va-ppc.h included with egcs and gcc-2.95.2
- To: Jason Kim <jwk2 at eecs dot lehigh dot edu>
- Subject: Re: patch for problem with va-ppc.h included with egcs and gcc-2.95.2
- From: "David A. Gatwood" <dgatwood at deepspace dot mklinux dot org>
- Date: Wed, 1 Dec 1999 11:43:47 -0800 (PST)
- cc: Franz Sirl <Franz dot Sirl-kernel at lauterbach dot com>, "linuxppc-dev at lists dot linuxppc dot org" <linuxppc-dev at lists dot linuxppc dot org>, "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>
On Wed, 1 Dec 1999, Jason Kim wrote:
> Having a fixed size array as a user accessible item (which is TYPEDEF'ed to
> resemble a structure, no less) which could be passed around is just a BAD idea
> in C/C++. I have yet to hear any concrete reasons (besides just plain
> obstinacy) why va_list HAS to be implemented this way.
Years of legacy binaries that would have to be rebuilt, for one. The fact
that we _just_ had a varargs-related rework of some programs (linux
kernel, mach kernel, etc. come to mind) for gcc 2.95.x is another reason.
Mucking with the way the compiler builds varargs can have really nasty
implications. It should not be changed for trivial reasons. The macros
are there to be used. Attempting to do anything else with varargs breaks
spec, and changing the compiler and everything ever built with it just to
make it easier for coders to be sloppy is a bad idea (tm).
David