public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Zack Weinberg <zack@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc/zack/more-obsolete-typedefs] Linux: Add oddly-named arm syscalls to syscall-names.list Date: Tue, 18 Jun 2019 15:28:00 -0000 [thread overview] Message-ID: <20190618152851.95673.qmail@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=0bb8f8c791862a4ff38a584af23bbb5bf3f90acd commit 0bb8f8c791862a4ff38a584af23bbb5bf3f90acd Author: Florian Weimer <fweimer@redhat.com> Date: Fri May 31 13:52:16 2019 +0200 Linux: Add oddly-named arm syscalls to syscall-names.list <asm/unistd.h> on arm defines the following macros: #define __ARM_NR_breakpoint (__ARM_NR_BASE+1) #define __ARM_NR_cacheflush (__ARM_NR_BASE+2) #define __ARM_NR_usr26 (__ARM_NR_BASE+3) #define __ARM_NR_usr32 (__ARM_NR_BASE+4) #define __ARM_NR_set_tls (__ARM_NR_BASE+5) #define __ARM_NR_get_tls (__ARM_NR_BASE+6) These do not follow the regular __NR_* naming convention and have so far been ignored by the syscall-names.list consistency checks. This commit adds these names to the file, preparing for the availability of these names in the regular __NR_* namespace. Diff: --- ChangeLog | 6 ++++++ sysdeps/unix/sysv/linux/syscall-names.list | 5 +++++ 2 files changed, 11 insertions(+) diff --git a/ChangeLog b/ChangeLog index b7b9203..88a34cf 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,9 @@ +2019-05-31 Florian Weimer <fweimer@redhat.com> + + * sysdeps/unix/sysv/linux/syscall-names.list: Add oddly named + system calls for the arm architecture: breakpoint, get_tls, + set_tls, usr26, usr32. + 2019-05-30 Gabriel F. T. Gomes <gabrielftg@linux.ibm.com> * sysdeps/powerpc/Makefile diff --git a/sysdeps/unix/sysv/linux/syscall-names.list b/sysdeps/unix/sysv/linux/syscall-names.list index 2d0354b..ae8adab 100644 --- a/sysdeps/unix/sysv/linux/syscall-names.list +++ b/sysdeps/unix/sysv/linux/syscall-names.list @@ -52,6 +52,7 @@ bdflush bind bpf break +breakpoint brk cachectl cacheflush @@ -139,6 +140,7 @@ get_kernel_syms get_mempolicy get_robust_list get_thread_area +get_tls getcpu getcwd getdents @@ -499,6 +501,7 @@ set_mempolicy set_robust_list set_thread_area set_tid_address +set_tls setdomainname setfsgid setfsgid32 @@ -611,6 +614,8 @@ unlinkat unshare uselib userfaultfd +usr26 +usr32 ustat utime utimensat
reply other threads:[~2019-06-18 15:28 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=20190618152851.95673.qmail@sourceware.org \ --to=zack@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).