diff options
| author | Tom Tromey <tromey@adacore.com> | 2019-11-25 11:14:50 -0700 |
|---|---|---|
| committer | Tom Tromey <tromey@adacore.com> | 2019-12-04 09:31:18 -0700 |
| commit | 7ab4a236ce85f1e0950e88e267e679a066b77bed (patch) | |
| tree | d59df6f09d15b5217ff986ff33a7019c34ba8081 /gdb/valarith.c | |
| parent | 103a685e7fd27bb1347a2459c07e648aac7a6f54 (diff) | |
| download | fsf-binutils-gdb-7ab4a236ce85f1e0950e88e267e679a066b77bed.zip fsf-binutils-gdb-7ab4a236ce85f1e0950e88e267e679a066b77bed.tar.gz fsf-binutils-gdb-7ab4a236ce85f1e0950e88e267e679a066b77bed.tar.bz2 | |
Move type_byte_order earlier
I failed to notice that the scalar_storage_order patch put
type_byte_order at the end of gdbtypes.c. The end of the file is
normally where the file's _initialize function goes. This moves
type_byte_order earlier, into a more relevant section.
gdb/ChangeLog
2019-12-04 Tom Tromey <tromey@adacore.com>
* gdbtypes.c (type_byte_order): Move earlier. Assert for unknown
endian-ness.
Change-Id: I4666431ecbb32ec98918f39f72d22c86b2bc8dde
Diffstat (limited to 'gdb/valarith.c')
0 files changed, 0 insertions, 0 deletions