gcc 3.1 broke the mangler again...  this time it seems gcc is adding
spurious writes to the stack in the prologue, triggered perhaps by
inline functions.  The code generated for uses of ASSIGN_DBL() and
ASSIGN_INT64() is really terrible - we should really submit a bug
report to the gcc folks for this one.

Anyway, this patch should get us going again; we now toss the spurious
instructions back into the main part of the code (just in case they
happened to be there for a good reason).