PATCH: Fix 2 PPC/SYSV varargs problems

Franz Sirl Franz.Sirl-kernel@lauterbach.com
Tue Jun 29 01:07:00 GMT 1999


At 00:21 28.06.99 , Richard Henderson wrote:
>On Sun, Jun 27, 1999 at 01:03:18PM -0700, Richard Henderson wrote:
> > We should just be implementing the algortithm exactly
> > as presented in the ABI manual.  It's clear enough.
>[...]
> > I'll give you another patch in a little bit.
>
>Try this out.  I'm starting an AIX bootstrap to see that I
>didn't break anything there.

With the changes mentioned in my last email, gcc-2.95pre bootstraps fine, 
but has some regressions in the testsuite:
FAIL: gcc.c-torture/execute/va-arg-3.c execution,  -O0
FAIL: gcc.c-torture/execute/va-arg-3.c execution,  -O1
FAIL: gcc.c-torture/execute/va-arg-3.c execution,  -O2
FAIL: gcc.c-torture/execute/va-arg-3.c execution,  -O3 -fomit-frame-pointer
FAIL: gcc.c-torture/execute/va-arg-3.c execution,  -O3 -fomit-frame-pointer 
-funroll-loops
FAIL: gcc.c-torture/execute/va-arg-3.c execution,  -O3 -fomit-frame-pointer 
-funroll-all-loops -finline-functions
FAIL: gcc.c-torture/execute/va-arg-3.c execution,  -O3 -g
FAIL: gcc.c-torture/execute/va-arg-3.c execution,  -Os
FAIL: g++.jason/thunk3.C (test for excess errors)
FAIL: g++.pt/vaarg.C (test for excess errors)

Looks like the !stdarg_p case handling needs some tweaking.

Franz.



More information about the Gcc-patches mailing list