From: Florian Weimer <fweimer@redhat.com>
To: libc-alpha@sourceware.org
Subject: [PATCH 09/11] Move sysdeps/gnu/unwind-resume.c to sysdeps/generic/unwind-resume.c
Date: Thu, 13 Feb 2020 17:08:00 -0000 [thread overview]
Message-ID: <13f33b49e69a5ed4e6723793c7cec36d48a2a929.1581613260.git.fweimer@redhat.com> (raw)
In-Reply-To: <cover.1581613260.git.fweimer@redhat.com>
This change allows architecture-specific sysdeps directories to override
it.
---
sysdeps/{gnu => generic}/unwind-resume.c | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename sysdeps/{gnu => generic}/unwind-resume.c (100%)
diff --git a/sysdeps/gnu/unwind-resume.c b/sysdeps/generic/unwind-resume.c
similarity index 100%
rename from sysdeps/gnu/unwind-resume.c
rename to sysdeps/generic/unwind-resume.c
--
2.24.1
next prev parent reply other threads:[~2020-02-13 17:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 17:08 [PATCH 00/11] Unify dynamic loading of the libgcc_s unwinder Florian Weimer
2020-02-13 17:08 ` [PATCH 08/11] __frame_state_for: Use <unwind-link.h> for unwinder access Florian Weimer
2020-02-13 17:08 ` [PATCH 07/11] s390: Implement backtrace on top of <unwind-link.h> Florian Weimer
2020-02-14 11:55 ` Stefan Liebler
2020-02-13 17:08 ` Florian Weimer [this message]
2020-02-13 17:08 ` [PATCH 03/11] arm: " Florian Weimer
2020-02-13 17:08 ` [PATCH 05/11] m68k: " Florian Weimer
2020-02-13 17:08 ` [PATCH 06/11] sparc: Implement backtrace on top <unwind-link.h> Florian Weimer
2020-02-13 17:08 ` [PATCH 02/11] backtrace: Implement on top of <unwind-link.h> Florian Weimer
2020-02-13 17:08 ` [PATCH 04/11] i386: Implement backtrace " Florian Weimer
2020-02-13 17:08 ` [PATCH 10/11] Implement _Unwind_Resume in libc " Florian Weimer
2020-02-13 17:08 ` [PATCH 01/11] Implement <unwind-link.h> for dynamically loading the libgcc_s unwinder Florian Weimer
2020-02-13 17:08 ` [PATCH 11/11] nptl: Use <unwind-link.h> for accessing " Florian Weimer
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=13f33b49e69a5ed4e6723793c7cec36d48a2a929.1581613260.git.fweimer@redhat.com \
--to=fweimer@redhat.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).