From: Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
To: libc-alpha@sourceware.org
Subject: [COMMITTED 3/3] nptl: Add missing cancellation flags on lockf
Date: Thu, 8 Oct 2020 10:30:15 -0300 [thread overview]
Message-ID: <20201008133015.68359-3-adhemerval.zanella@linaro.org> (raw)
In-Reply-To: <20201008133015.68359-1-adhemerval.zanella@linaro.org>
It also removes CFLAGS-lockf.c duplicate rule. It fixes
nptl/tst-cancelx16 on mips64-linux-gnu.
---
io/Makefile | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/io/Makefile b/io/Makefile
index cf380f3516..36ac06070a 100644
--- a/io/Makefile
+++ b/io/Makefile
@@ -93,7 +93,8 @@ CFLAGS-fcntl.c += -fexceptions -fasynchronous-unwind-tables
CFLAGS-fcntl64.c += -fexceptions -fasynchronous-unwind-tables
CFLAGS-poll.c += -fexceptions -fasynchronous-unwind-tables
CFLAGS-ppoll.c += -fexceptions -fasynchronous-unwind-tables
-CFLAGS-lockf.c += -fexceptions
+CFLAGS-lockf.c += -fexceptions -fasynchronous-unwind-tables
+CFLAGS-lockf64.c += -fexceptions -fasynchronous-unwind-tables
CFLAGS-statfs.c += -fexceptions
CFLAGS-fstatfs.c += -fexceptions
CFLAGS-statvfs.c += -fexceptions
@@ -102,7 +103,6 @@ CFLAGS-fts.c += -Wno-uninitialized $(uses-callbacks) -fexceptions
CFLAGS-fts64.c += -Wno-uninitialized $(uses-callbacks) -fexceptions
CFLAGS-ftw.c += $(uses-callbacks) -fexceptions
CFLAGS-ftw64.c += $(uses-callbacks) -fexceptions
-CFLAGS-lockf.c += -fexceptions
CFLAGS-posix_fallocate.c += -fexceptions
CFLAGS-posix_fallocate64.c += -fexceptions
CFLAGS-fallocate.c += -fexceptions
--
2.25.1
prev parent reply other threads:[~2020-10-08 13:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 13:30 [COMMITTED 1/3] Update alpha libm-test-ulps Adhemerval Zanella via Libc-alpha
2020-10-08 13:30 ` [COMMITTED 2/3] Update mips64 libm-test-ulps Adhemerval Zanella via Libc-alpha
2020-10-08 13:30 ` Adhemerval Zanella via Libc-alpha [this message]
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=20201008133015.68359-3-adhemerval.zanella@linaro.org \
--to=libc-alpha@sourceware.org \
--cc=adhemerval.zanella@linaro.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).