From: "Dmitry V. Levin" <ldv@altlinux.org>
To: libc-alpha@sources.redhat.com
Cc: linux-gcc@vger.kernel.org
Subject: Re: Why __memrchr vs. memrchr ?
Date: Tue, 3 Feb 2004 01:17:23 +0300 [thread overview]
Message-ID: <20040202221723.GD11571@basalt.office.altlinux.org> (raw)
In-Reply-To: <20040203023721.A20354@zzz.ward.six>
[-- Attachment #1: Type: text/plain, Size: 395 bytes --]
Hi,
On Tue, Feb 03, 2004 at 02:37:21AM +0500, Denis Zaitsev wrote:
> Why such a scheme is used in GLIBC:
>
> declare + define __memrchr, and than
>
> # ifdef __USE_GNU
> # define memrchr(s, c, n) __memrchr ((s), (c), (n))
> # endif
>
> ? memrchr is not the GNU extension, is it?
According to memchr(3),
"The memrchr() function is a GNU extension, available since glibc 2.1.91".
--
ldv
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-02-02 22:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-02 21:37 Why __memrchr vs. memrchr ? Denis Zaitsev
2004-02-02 22:17 ` Dmitry V. Levin [this message]
2004-02-03 0:30 ` Denis Zaitsev
2004-02-03 6:03 ` Andreas Jaeger
2004-02-06 0:08 ` Denis Zaitsev
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=20040202221723.GD11571@basalt.office.altlinux.org \
--to=ldv@altlinux.org \
--cc=libc-alpha@sources.redhat.com \
--cc=linux-gcc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.