The solution is to hack gcc to provide a *pure extension* called, perhaps,
__int64_t, and use that for the quad type; then no code needs to know about
it, and we aren't producing syntax errors.

__int64_t invokes undefined behavior, but it's not a syntax error, so it's
fine to use it even in -ansi -pedantic.

We may want to look at migrating to C9X-style <inttypes.h> support,
especially because the long long rules are changing as we speak, to
avoid some of the cruft inherent int most current implementations.

-s