Mark Wielaard <[email protected]> writes: > Is there a canonical ELF/gabi processor spec for m68k?
Not online, AFAIK. I have a paper copy of the m68k SysV ABI supplement, but it doesn't contain anything related to DWARF. > If so it would be good to add an URL in e.g. m68k_regs.c so others can > easily lookup the register mappings described there. If the only > "official" documentation is in GCC or binutils/gdb that would also be > good to mention. In effect, gcc is the canonical source of information. > How does the make check result look on m68k with this patch applied? SKIP: run-addr2line-i-demangle-test.sh SKIP: run-backtrace-native.sh SKIP: run-backtrace-data.sh SKIP: run-backtrace-dwarf.sh SKIP: run-backtrace-native-biarch.sh SKIP: run-backtrace-native-core.sh SKIP: run-backtrace-native-core-biarch.sh SKIP: run-backtrace-demangle.sh SKIP: run-stack-demangled-test.sh SKIP: run-deleted.sh ============================================================================ Testsuite summary for elfutils 0.164 ============================================================================ # TOTAL: 145 # PASS: 135 # SKIP: 10 # XFAIL: 0 # FAIL: 0 # XPASS: 0 # ERROR: 0 > Could you provide testcases/files for run-readelf-mixed-corenote.sh, > run-allregs.sh, run-strip-test?.sh and/or run-strip-reloc.sh. That way > people can run make check on a non-m68k setup and see whether m68k ELF > files are handled properly. Yes, I can do that. > If you are ambitious you could also add support for backtraces by > implementing m68k_init_reg.c set_initial_registers_tid, m68k_cfi.c > abi_cfi, frame_nregs. My first goal was to get a clean testsuite, but I'll continue to work on the optional parts. Andreas. -- Andreas Schwab, [email protected] GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."
