patch: alpha haifa abort

[John Carr]

> or do you want both __load_big_endian() and __load_little_endian() with
> GCC creating a no-op load for the case matching the target's
> byte-endianness? 

I want explicitly big- and little-endian loads and stores.  I think it
is rare to want to swap bytes regardless of the current byte order.
Usually one is doing networking (big-endian) or PCI (little-endian)
and wants to write in a specific byte order.