public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Adhemerval Zanella <azanella@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc] linux: Remove __ASSUME_ATFCTS Date: Wed, 2 Sep 2020 13:01:49 +0000 (GMT) [thread overview] Message-ID: <20200902130149.0918D3870891@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=bbedd75c41ff801c7606bbaf1b7bdfc45d3f45a5 commit bbedd75c41ff801c7606bbaf1b7bdfc45d3f45a5 Author: Adhemerval Zanella <adhemerval.zanella@linaro.org> Date: Tue Aug 25 16:57:12 2020 -0300 linux: Remove __ASSUME_ATFCTS The __have_atfcts is not used anywhere. Checked on x86_64-linux-gnu. Diff: --- io/openat.c | 5 ----- sysdeps/unix/sysv/linux/kernel-features.h | 4 ---- 2 files changed, 9 deletions(-) diff --git a/io/openat.c b/io/openat.c index a7ce65bee2..2f5a9f04de 100644 --- a/io/openat.c +++ b/io/openat.c @@ -23,11 +23,6 @@ #include <sys/stat.h> #include <kernel-features.h> -/* Some mostly-generic code (e.g. sysdeps/posix/getcwd.c) uses this variable - if __ASSUME_ATFCTS is not defined. */ -#ifndef __ASSUME_ATFCTS -int __have_atfcts; -#endif /* Open FILE with access OFLAG. Interpret relative paths relative to the directory associated with FD. If O_CREAT or O_TMPFILE is in OFLAG, a diff --git a/sysdeps/unix/sysv/linux/kernel-features.h b/sysdeps/unix/sysv/linux/kernel-features.h index a6bbc3c94e..e648eecc0d 100644 --- a/sysdeps/unix/sysv/linux/kernel-features.h +++ b/sysdeps/unix/sysv/linux/kernel-features.h @@ -49,10 +49,6 @@ SH this appeared first in 2.6.19-rc1, on ia64 in 2.6.22-rc1. */ #define __ASSUME_PSELECT 1 -/* The *at syscalls were introduced just after 2.6.16-rc1. On PPC - they were introduced in 2.6.17-rc1, on SH in 2.6.19-rc1. */ -#define __ASSUME_ATFCTS 1 - /* Support for inter-process robust mutexes was added in 2.6.17 (but some architectures lack futex_atomic_cmpxchg_inatomic in some configurations). */
reply other threads:[~2020-09-02 13:01 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200902130149.0918D3870891@sourceware.org \ --to=azanella@sourceware.org \ --cc=glibc-cvs@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: linkBe 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).