Rewrite the varags implementation again (third time's the charm), the upstream

varagrs implementation being utterly wrong.

This is the same logic as the one I wrote for gcc 2.95, with a few more
optimizations whenever possible (such as not outputting instructions to fill
fields of the __va_list struct we know won't be accessed, now that we have
total control of the struct in the compiler).

It should now be possible to mix varags code compiled by gcc 2.95, with code
compiled with gcc 3, with the following exception: as I have finally found and
fixed the buglet causing all arguments to be passed on the stack if any of the
named arguments (before varargs) is a struct of 32 bytes or more passed by
value, such a (pretty uncommon) case will not be interoperable. One such case
can be found as va-arg-4.c in gcc's testsuite.

With these changes, all the following varargs exercizers from gcc's testsuite
now pass when compiled with the in-tree gcc 3:
  gcc.c-torture/execute/920625-1.c
  gcc.c-torture/execute/931004-10.c
  gcc.c-torture/execute/931004-12.c
  gcc.c-torture/execute/931004-14.c
  gcc.c-torture/execute/931004-4.c
  gcc.c-torture/execute/931004-6.c
  gcc.c-torture/execute/931004-8.c
  gcc.c-torture/execute/strct-varg-2.c
  gcc.c-torture/execute/va-arg-1.c
  gcc.c-torture/execute/va-arg-2.c
  gcc.c-torture/execute/va-arg-4.c
  gcc.c-torture/execute/va-arg-5.c
  gcc.c-torture/execute/va-arg-6.c
as well as the few others of my own I had been using while working on gcc 2.95
more than 8 years ago.

0 files changed, 0 insertions, 0 deletions