public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "adhemerval.zanella at linaro dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/28883] sysdeps/unix/sysv/linux/select.c: __select64 !__ASSUME_TIME64_SYSCALLS && !__ASSUME_PSELECT fails on Microblaze Date: Wed, 16 Feb 2022 14:07:42 +0000 [thread overview] Message-ID: <bug-28883-131-yhvvKg7WwJ@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28883-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28883 Adhemerval Zanella <adhemerval.zanella at linaro dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adhemerval.zanella at linaro dot o | |rg --- Comment #1 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> --- It would be good if Linux UAPI could clean this up and advertise the real supported syscall, so consumers would not require to add such hacks. I will push a slight different patch (below), it documents microblaze difference and gives glibc a consistent view of the supported syscalls. PS: next time please send the patch to libc-alpha maillist, we don't apply patch that were only attached in the bugzilla. --- diff --git a/sysdeps/unix/sysv/linux/microblaze/arch-syscall.h b/sysdeps/unix/sysv/linux/microblaze/arch-syscall.h index 6e10c3661d..06c0575325 100644 --- a/sysdeps/unix/sysv/linux/microblaze/arch-syscall.h +++ b/sysdeps/unix/sysv/linux/microblaze/arch-syscall.h @@ -313,7 +313,7 @@ #define __NR_sched_setscheduler 156 #define __NR_sched_yield 158 #define __NR_seccomp 384 -#define __NR_select 82 +#define __NR_select 142 #define __NR_semctl 328 #define __NR_semget 329 #define __NR_semop 330 diff --git a/sysdeps/unix/sysv/linux/microblaze/fixup-asm-unistd.h b/sysdeps/unix/sysv/linux/microblaze/fixup-asm-unistd.h new file mode 100644 index 0000000000..6103a5c13e --- /dev/null +++ b/sysdeps/unix/sysv/linux/microblaze/fixup-asm-unistd.h @@ -0,0 +1,23 @@ +/* Regularize <asm/unistd.h> definitions. Microblaze version. + Copyright (C) 2022 Free Software Foundation, Inc. + + The GNU C Library is free software; you can redistribute it and/or + modify it under the terms of the GNU Lesser General Public + License as published by the Free Software Foundation; either + version 2.1 of the License, or (at your option) any later version. + + The GNU C Library is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU + Lesser General Public License for more details. + + You should have received a copy of the GNU Lesser General Public + License along with the GNU C Library; if not, see + <http://www.gnu.org/licenses/>. */ + +/* Microblaze does not implement __NR_select, besides kernel advertise + it. */ +#ifdef __NR_select +# undef __NR_select +# define __NR_select __NR__newselect +#endif -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-02-16 14:07 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-12 1:18 [Bug libc/28883] New: " mark.hatle at kernel dot crashing.org 2022-02-16 14:07 ` adhemerval.zanella at linaro dot org [this message] 2022-02-16 19:46 ` [Bug libc/28883] " adhemerval.zanella at linaro dot org
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=bug-28883-131-yhvvKg7WwJ@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@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).