From: Jakub Jelinek via Libc-alpha <libc-alpha@sourceware.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org, gcc-patches@gcc.gnu.org,
Jason Merrill <jason@redhat.com>
Subject: Re: [PATCH 1/4] libgcc: Remove tbase member from struct unw_eh_callback_data
Date: Thu, 18 Nov 2021 14:47:59 +0100 [thread overview]
Message-ID: <20211118134759.GC2646553@tucnak> (raw)
In-Reply-To: <eb8f3783f4345df6bf08431cac2fe7bb81421898.1635955148.git.fweimer@redhat.com>
On Wed, Nov 03, 2021 at 05:28:35PM +0100, Florian Weimer wrote:
> It is always a null pointer.
>
> libgcc/ChangeLog
>
> * unwind-dw2-fde-dip.c (struct unw_eh_callback_data): Remove
> tbase member.
> (base_from_cb_data): Adjust.
> (_Unwind_IteratePhdrCallback): Likewise.
> (_Unwind_Find_FDE): Likewise.
Ok.
Jakub
next prev parent reply other threads:[~2021-11-18 13:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 16:28 [PATCH 0/4] Use _dl_find_eh_frame to locate DWARF EH data in the unwinder Florian Weimer via Libc-alpha
2021-11-03 16:28 ` [PATCH 1/4] libgcc: Remove tbase member from struct unw_eh_callback_data Florian Weimer via Libc-alpha
2021-11-18 13:47 ` Jakub Jelinek via Libc-alpha [this message]
2021-11-03 16:28 ` [PATCH 2/4] libgcc: Remove dbase member from struct unw_eh_callback_data if NULL Florian Weimer via Libc-alpha
2021-11-18 14:33 ` Jakub Jelinek via Libc-alpha
2021-11-03 16:28 ` [PATCH 3/4] libgcc: Split FDE search code from PT_GNU_EH_FRAME lookup Florian Weimer via Libc-alpha
2021-11-18 15:21 ` Jakub Jelinek via Libc-alpha
2021-11-23 17:56 ` Florian Weimer via Libc-alpha
2021-11-25 17:16 ` Jakub Jelinek via Libc-alpha
2021-11-03 16:28 ` [PATCH 4/4] libgcc: Use _dl_find_eh_frame in _Unwind_Find_FDE Florian Weimer via Libc-alpha
2021-11-18 15:45 ` Jakub Jelinek via Libc-alpha
2021-11-25 20:42 ` Florian Weimer via Libc-alpha
2021-11-26 15:49 ` Jakub Jelinek via Libc-alpha
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=20211118134759.GC2646553@tucnak \
--to=libc-alpha@sourceware.org \
--cc=fweimer@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jason@redhat.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).