libecpg (8.0 and CVS) hits a gcc bug on powerpc and amd64 (crash) - Mailing list pgsql-interfaces

From Christof Petig
Subject libecpg (8.0 and CVS) hits a gcc bug on powerpc and amd64 (crash)
Date
Msg-id 42383EE8.5070503@petig-baender.de
Whole thread Raw
Responses Re: libecpg (8.0 and CVS) hits a gcc bug on powerpc
Re: libecpg (8.0 and CVS) hits a gcc bug on powerpc and amd64 (crash)
List pgsql-interfaces
NB: The crossposting is actually suggested on the mailing list description:
"If you've found a bug in PostgreSQL, please send it both to this list
and also to the pgsql-patches list."

Amd64 and powerpc share an ABI design which enables variable passing in
registers and which makes va_list a complex datatype. Due to gcc not
implementing a part of the C9x standard
(http://mail-index.netbsd.org/tech-toolchain/2003/11/11/0011.html)
taking a pointer to a va_list will fail on these platforms. The
corresponding bug (http://gcc.gnu.org/bugzilla/show_bug.cgi?id=8262) is
closed, so the gcc developers seem not to plan to change this.

So I propose the following hack (feel free to improve it!) to go into
mainline. Since only powerpc and amd64 are affected (and the old method
does not work at all here at all) the patch should not be controversial.

    Christof

PS: I don't know about other architectures. I can't believe that only
ppc and amd64 pass parameters in registers.
PPS: I could not test it on amd64, but all docs indicate the same behaviour.

Attachment

pgsql-interfaces by date:

Previous
From: Michael Fuhr
Date:
Subject: Re: Check before insert
Next
From: Christof Petig
Date:
Subject: Re: libecpg (8.0 and CVS) hits a gcc bug on powerpc