From: Florian Weimer <fweimer@redhat.com>
To: libc-alpha@sourceware.org
Cc: Jakub Jelinek <jakub@redhat.com>, "H.J. Lu" <hjl.tools@gmail.com>
Subject: [PATCH 0/2] Remove some i386 system call optimizations
Date: Tue, 11 Jan 2022 11:05:08 +0100 [thread overview]
Message-ID: <cover.1641895400.git.fweimer@redhat.com> (raw)
The configure check for CAN_USE_REGISTER_ASM_EBP is unreliable. And we
used it to switch away from using %ebx in assembler constraints, but
this appears to be no longer necessary.
Tested on i686-linux-gnu. Built with build-many-glibcs.py.
Thanks,
Florian
Florian Weimer (2):
i386: Always treat %ebx as an allocatable register
i386: Always use __libc_do_syscall for 6-argument syscalls (bug 27997)
config.h.in | 4 -
sysdeps/unix/sysv/linux/i386/configure | 39 ----
sysdeps/unix/sysv/linux/i386/configure.ac | 17 --
sysdeps/unix/sysv/linux/i386/sysdep.h | 222 +++-------------------
4 files changed, 27 insertions(+), 255 deletions(-)
base-commit: e72ef23ee88187284b4b1ca9b2e314e618429d35
--
2.34.1
next reply other threads:[~2022-01-11 10:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 10:05 Florian Weimer [this message]
2022-01-11 10:06 ` [PATCH 1/2] i386: Always treat %ebx as an allocatable register Florian Weimer
2022-01-11 10:06 ` [PATCH 2/2] i386: Always use __libc_do_syscall for 6-argument syscalls (bug 27997) Florian Weimer
2022-01-11 14:00 ` [PATCH 0/2] Remove some i386 system call optimizations H.J. Lu
2022-01-11 20:30 ` H.J. Lu
2022-01-11 20:37 ` Florian Weimer
2022-01-11 22:20 ` H.J. Lu
2022-01-11 22:52 ` Florian Weimer
2022-01-12 18:49 ` H.J. Lu
2022-01-12 19:37 ` Florian Weimer
2022-01-12 19:56 ` H.J. Lu
2022-01-12 20:12 ` Florian Weimer
2022-01-12 21:59 ` H.J. Lu
2022-01-12 22:33 ` 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=cover.1641895400.git.fweimer@redhat.com \
--to=fweimer@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=jakub@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).