From: Jakub Jelinek <jakub@redhat.com>
To: Roland McGrath <roland@redhat.com>
Cc: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: [PATCH] __sched_yield libc_hidden_def
Date: Thu, 23 Feb 2006 13:56:00 -0000 [thread overview]
Message-ID: <20060223135632.GA30252@sunsite.mff.cuni.cz> (raw)
Hi!
Ulrich added libc_hidden_proto to __sched_yield last month.
While that works when __sched_yield is provided by syscalls.list
(as in that case __GI___sched_yield is provided automatically),
when it is implemented in C, we need to mark it.
2006-02-23 Jakub Jelinek <jakub@redhat.com>
* posix/sched_yield.c (__sched_yield): Add libc_hidden_def.
* sysdeps/mach/sched_yield.c (__sched_yield): Likewise.
--- libc/posix/sched_yield.c.jj 2005-12-14 11:39:15.000000000 +0100
+++ libc/posix/sched_yield.c 2006-02-23 14:48:34.000000000 +0100
@@ -1,4 +1,4 @@
-/* Copyright (C) 1996, 1997 Free Software Foundation, Inc.
+/* Copyright (C) 1996, 1997, 2006 Free Software Foundation, Inc.
This file is part of the GNU C Library.
The GNU C Library is free software; you can redistribute it and/or
@@ -28,6 +28,7 @@ __sched_yield (void)
return -1;
}
stub_warning (sched_yield)
+libc_hidden_def (__sched_yield)
weak_alias (__sched_yield, sched_yield)
#include <stub-tag.h>
--- libc/sysdeps/mach/sched_yield.c.jj 2001-07-06 06:55:56.000000000 +0200
+++ libc/sysdeps/mach/sched_yield.c 2006-02-23 14:49:07.000000000 +0100
@@ -1,5 +1,5 @@
/* sched_yield -- yield the processor. Mach version.
- Copyright (C) 2000 Free Software Foundation, Inc.
+ Copyright (C) 2000, 2006 Free Software Foundation, Inc.
This file is part of the GNU C Library.
The GNU C Library is free software; you can redistribute it and/or
@@ -28,4 +28,5 @@ __sched_yield (void)
(void) __swtch ();
return 0;
}
+libc_hidden_def (__sched_yield)
weak_alias (__sched_yield, sched_yield)
Jakub
reply other threads:[~2006-02-23 13:56 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=20060223135632.GA30252@sunsite.mff.cuni.cz \
--to=jakub@redhat.com \
--cc=libc-hacker@sources.redhat.com \
--cc=roland@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).