From: Alexandre Oliva <aoliva@redhat.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Jakub Jelinek <jakub@redhat.com>, Andreas Jaeger <aj@suse.de>,
GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: Re: Fix _exit for Linux
Date: Tue, 24 Sep 2002 20:24:00 -0000 [thread overview]
Message-ID: <orptv2eooy.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <3D861180.2070903@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 832 bytes --]
On Sep 16, 2002, Ulrich Drepper <drepper@redhat.com> wrote:
> Jakub Jelinek wrote:
>> There is a difference between libc_hidden_def in .S files and in .c files.
>> In .S files it will work even if libc_hidden_proto () was not declared
>> in header files (usually the assembly doesn't even include those headers),
>> while if you use libc_hidden_{def,weak} without previous libc_hidden_proto,
>> things will break badly...
> Anyway, the _exit code can now be hidden. The implementation in glibc
> itself is now correct if compiled with the new kernel headers so there
> is no need to allow it to be overwritten. Let's change
> include/unistd.h and add hidden everywhere for _exit.
Apologies for the delay. Here's the patch that fixes the mips port
such that libc.so doesn't fail to link because __syscall_exit is not
defined.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: glibc-mips-_exit.patch --]
[-- Type: text/x-patch, Size: 834 bytes --]
Index: ChangeLog
from Alexandre Oliva <aoliva@redhat.com>
* sysdeps/unix/sysv/linux/mips/syscalls.list: Added _exit.
Index: sysdeps/unix/sysv/linux/mips/syscalls.list
===================================================================
RCS file: /cvs/glibc/libc/sysdeps/unix/sysv/linux/mips/syscalls.list,v
retrieving revision 1.32
diff -u -p -r1.32 syscalls.list
--- sysdeps/unix/sysv/linux/mips/syscalls.list 13 Sep 2002 07:12:28 -0000 1.32
+++ sysdeps/unix/sysv/linux/mips/syscalls.list 25 Sep 2002 03:23:27 -0000
@@ -82,3 +82,6 @@ sys_lstat lxstat lstat i:sp __syscall_l
sys_readv readv readv i:ipi __syscall_readv
sys_stat xstat stat i:sp __syscall_stat
sys_writev writev writev i:ipi __syscall_writev
+
+# _exit() does INLINE_SYSCALL (_exit), but we don't have INLINE_SYSCALL
+sys_exit _exit exit i:i __syscall_exit
[-- Attachment #3: Type: text/plain, Size: 289 bytes --]
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist Professional serial bug killer
next prev parent reply other threads:[~2002-09-25 3:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-15 20:40 Andreas Jaeger
2002-09-15 22:11 ` Ulrich Drepper
2002-09-15 23:56 ` Roland McGrath
2002-09-16 0:10 ` Ulrich Drepper
2002-09-16 0:36 ` Roland McGrath
2002-09-16 0:45 ` Ulrich Drepper
2002-09-16 9:46 ` Alexandre Oliva
2002-09-16 9:37 ` Andreas Jaeger
2002-09-16 9:52 ` Alexandre Oliva
2002-09-16 9:54 ` Jakub Jelinek
2002-09-16 10:14 ` Ulrich Drepper
2002-09-24 20:24 ` Alexandre Oliva [this message]
2002-09-24 20:28 ` Roland McGrath
2002-09-24 20:35 ` Ulrich Drepper
2002-09-24 21:08 ` Roland McGrath
2002-09-24 21:53 ` Ulrich Drepper
2002-09-24 22:02 ` Roland McGrath
2002-09-24 21:55 ` Alexandre Oliva
2002-09-24 22:01 ` Roland McGrath
2002-09-25 10:27 ` Andreas Jaeger
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=orptv2eooy.fsf@free.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=aj@suse.de \
--cc=drepper@redhat.com \
--cc=jakub@redhat.com \
--cc=libc-hacker@sources.redhat.com \
/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).