From: Alexandre Oliva <aoliva@redhat.com>
To: James Lee <aeggie_dragon@yahoo.com>
Cc: gcc@gcc.gnu.org
Subject: Re: mapping between system calls and libc functions
Date: Mon, 27 Jan 2003 11:43:00 -0000 [thread overview]
Message-ID: <or7kcr9gfp.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <20030127005607.39702.qmail@web21307.mail.yahoo.com>
On Jan 26, 2003, James Lee <aeggie_dragon@yahoo.com> wrote:
> Where can I find the information about mapping between
> system calls and glibs functions?
Certainly not in this mailing list, whose purpose is to discuss the
development of GCC. The implementation of the C library is separate,
GCC just uses whatever C library come with the OS you're using.
--
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
prev parent reply other threads:[~2003-01-27 8:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-27 5:28 James Lee
2003-01-27 11:43 ` Alexandre Oliva [this message]
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=or7kcr9gfp.fsf@free.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=aeggie_dragon@yahoo.com \
--cc=gcc@gcc.gnu.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).