From: Andreas Schwab <schwab@linux-m68k.org>
To: elfutils-devel@lists.fedorahosted.org
Subject: Re: [PATCH] Add support for m68k
Date: Mon, 23 May 2016 19:01:35 +0200 [thread overview]
Message-ID: <87zirgvhcg.fsf@linux-m68k.org> (raw)
In-Reply-To: 1464004736.8441.143.camel@redhat.com
[-- Attachment #1: Type: text/plain, Size: 1934 bytes --]
Mark Wielaard <mjw@redhat.com> 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, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next reply other threads:[~2016-05-23 17:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 17:01 Andreas Schwab [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-05-24 11:52 Mark Wielaard
2016-05-23 11:58 Mark Wielaard
2016-05-20 17:37 Andreas Schwab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zirgvhcg.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=elfutils-devel@lists.fedorahosted.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).