public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>,
	Paul E Murphy <murphyp@linux.ibm.com>,
	Florian Weimer <fweimer@redhat.com>,
	Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH] powerpc: Remove backtrace implementation
Date: Thu, 15 Apr 2021 17:44:18 -0300	[thread overview]
Message-ID: <12ac2270-c3af-a364-ad12-367220991d06@linaro.org> (raw)
In-Reply-To: <87y2djzk1a.fsf@linux.ibm.com>



On 15/04/2021 11:42, Tulio Magno Quites Machado Filho wrote:
> Paul E Murphy via Libc-alpha <libc-alpha@sourceware.org> writes:
> 
>> Ping?  This seems like a beneficial change.  Using the unwind
>> information makes for a much more robust backtrace with other languages
>> which support C bindings but do not use the same ABI (specifically
>> calling to and from go code in C).
>>
>> Should we instead turn the existing ppc backtrace into a compat symbol?
>> This seems like it would address Tulio's issue with older binaries.
> 
> If we do this, we'll never be able to remove the old implementation, which was
> Adhemerval's goal.
> I particularly agree that duplicated code should be removed and I believe it
> would be helpful if libgcc had the fallback code.
> 

As before, I don't think this is a ABI breaker and making powerpc align
with other architecture simplifies the code and align the expectation.

And afaik all projects that do require fast unwinder do it themselves
(libsanitizer for instance) instead.

  reply	other threads:[~2021-04-15 20:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-12 17:09 Adhemerval Zanella
2021-02-12 17:21 ` Florian Weimer
2021-02-12 17:25   ` Adhemerval Zanella
2021-02-22 22:16     ` Tulio Magno Quites Machado Filho
2021-02-23  9:52       ` Florian Weimer
2021-02-23 11:56       ` Adhemerval Zanella
2021-02-23 12:28         ` Florian Weimer
2021-02-23 12:43           ` Adhemerval Zanella
2021-02-26 17:39             ` Raoni Fassina Firmino
2021-04-14 21:37               ` Paul E Murphy
2021-04-15 14:42                 ` Tulio Magno Quites Machado Filho
2021-04-15 20:44                   ` Adhemerval Zanella [this message]
2021-04-27 15:09                     ` Florian Weimer
2021-10-14 20:24                   ` Raphael M Zinsly
2021-10-14 21:39                     ` Tulio Magno Quites Machado Filho
2021-10-20 13:39                       ` Adhemerval Zanella
2021-02-26 17:19 ` Raoni Fassina Firmino

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=12ac2270-c3af-a364-ad12-367220991d06@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=murphyp@linux.ibm.com \
    --cc=tuliom@linux.ibm.com \
    /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).