From: Mark Wielaard <mark@klomp.org>
To: Jim Wilson <jimw@sifive.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] RISC-V: Fix elfutils testsuite unwind failures.
Date: Tue, 22 Jan 2019 14:28:45 +0100 [thread overview]
Message-ID: <5c03692dd8c9b1f230487a2a5b75ce5024a7d54c.camel@klomp.org> (raw)
In-Reply-To: <CAFyWVaY=EcAMpW8Qn+-i9iqFtuaa0jrFGoFABwSYxKSJFnp0EQ@mail.gmail.com>
On Sun, 2019-01-20 at 21:55 -0800, Jim Wilson wrote:
> Or maybe my glibc is configured slightly differently than the
> system glibc and that is effecting the result.
The distro might build with -fasynchronous-unwind-tables which would
make sure that only the CFI unwinder is used, while without it, it
might be that there is a frame that might have to be handled by the
fallback unwinder.
> I do think the __thead_start change and the new testcase are correct.
> Other ports have similar changes to __thread_start, and verifying
> that unwind to top of stack in a thread works is a good test to do.
Agreed,
Mark
next prev parent reply other threads:[~2019-01-22 13:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-13 23:48 [PATCH] RISC-V: Fix elfutils testsuite unwind failures Jim Wilson
2019-01-14 13:38 ` Florian Weimer
2019-01-14 17:29 ` Jim Wilson
2019-01-17 17:05 ` Mark Wielaard
2019-01-21 5:55 ` Jim Wilson
2019-01-22 13:28 ` Mark Wielaard [this message]
2019-01-23 6:58 ` Jim Wilson
2019-01-24 2:51 ` Palmer Dabbelt
2019-01-28 21:18 ` Jim Wilson
2019-01-28 22:44 ` DJ Delorie
2019-01-28 23:10 ` Jim Wilson
2019-02-04 22:37 ` DJ Delorie
2019-02-04 23:01 ` Jim Wilson
2019-02-04 23:33 ` DJ Delorie
2019-02-04 23:46 ` Joseph Myers
2019-02-04 23:57 ` DJ Delorie
2019-02-05 0:01 ` Joseph Myers
2019-02-12 20:08 ` ping^2 " Jim Wilson
2019-02-13 12:03 ` Andreas Schwab
2019-02-13 16:33 ` Andreas Schwab
2019-02-13 22:25 ` Palmer Dabbelt
2019-02-18 9:56 ` 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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5c03692dd8c9b1f230487a2a5b75ce5024a7d54c.camel@klomp.org \
--to=mark@klomp.org \
--cc=jimw@sifive.com \
--cc=libc-alpha@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).