Daniel Jacobowitz wrote:
> So, if you've got a symbol file and the endianness is set wrong, you
> can do this.  I guess that counts as going out of their way, but it
> doesn't match what you wrote originally, which was that you could never
> produce such internalvars.

Ah well, there's always another, more devious, way to do everything.
But, as you say, once the symbol table is loaded there ought to be no
endian issues unless the user brings it on themselves.

The patch solves the problem where built-in types are set before the
file is loaded, which is what I wanted to fix.

>> I don't actually know of a host/target where
>> this is a problem, but I'm sure there are some out there.
> 
> Where switching endianness affects the floating point format? 
> Everything but ARM FPA, as far as I know.

Well, I've tested it on x86 and sh4, and on both those platforms you can
'set endian ..' as much as you like and the floats are always shown
correctly. On a Sparc the numbers do come through garbled in the wrong
endian.

> Could you put spaces around the equals signs, please.
> 
> OK with that change.

Thanks, committed with that change.

The final patch is attached.

Andrew Stubbs