From: "kurt at roeckx dot be" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug backends/23902] varlocs dwarf_cfi_addrframe: unknown error (missing ebl abi_cfi hook)
Date: Sun, 30 Dec 2018 21:53:00 -0000 [thread overview]
Message-ID: <bug-23902-10460-gsg5WYkJOD@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23902-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=23902
--- Comment #10 from Kurt Roeckx <kurt at roeckx dot be> ---
In the mean time, I know the patch for mips was wrong, but the test suite seems
to be happy with the current patch. Mips has many different ABIs, and I've
mixed them up. The callee-saved registers aren't the same in all ABIs, there
are small differences.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2018-12-30 21:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 20:26 [Bug backends/23902] New: varlocs dwarf_cfi_addrframe: unknown error kurt at roeckx dot be
2018-11-21 12:25 ` [Bug backends/23902] " mark at klomp dot org
2018-11-21 19:16 ` kurt at roeckx dot be
2018-11-23 9:09 ` mark at klomp dot org
2018-11-23 17:49 ` kurt at roeckx dot be
2018-11-23 20:38 ` mark at klomp dot org
2018-11-23 20:45 ` kurt at roeckx dot be
2018-11-26 10:45 ` [Bug backends/23902] varlocs dwarf_cfi_addrframe: unknown error (missing ebl abi_cfi hook) mark at klomp dot org
2018-11-28 13:05 ` mark at klomp dot org
2018-12-30 19:53 ` kurt at roeckx dot be
2018-12-30 21:53 ` kurt at roeckx dot be [this message]
2019-02-14 22:11 ` [Bug backends/23902] MIPS " mark at klomp dot org
2019-07-10 10:44 ` mark at klomp dot org
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=bug-23902-10460-gsg5WYkJOD@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@sourceware.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).