From: Ralf Baechle <ralf@oss.sgi.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andreas Jaeger <aj@suse.de>, Mike Klar <mfklar@ponymail.com>,
linux-mips@oss.sgi.com, linux-mips@fnet.fr,
linux-mips@vger.rutgers.edu
Subject: Re: errno assignment in _syscall macros and glibc
Date: Sun, 25 Jun 2000 23:48:33 +0200 [thread overview]
Message-ID: <20000625234833.B3802@bacchus.dhis.org> (raw)
In-Reply-To: <E136JuZ-0003C0-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Sun, Jun 25, 2000 at 10:25:48PM +0100
On Sun, Jun 25, 2000 at 10:25:48PM +0100, Alan Cox wrote:
> > Sure; these days glibc is more or less synonym with libc and I was using
> > it in that sense.
> >
> > What small, portable libcs do we have available anyway? Some mipers will
> > want one.
>
> I've been playing with the Linux8086 libc which is tiny but not portable when
> Prumpf pointed out that Cygnus newlib is designed for precisely this job. Its
> about 250K MIPS32 (my PDA has mips32/mips64 but not mips16 - duh!!)
Oh promised lands of small happy libcs :-)
Back to the original problem - the i386 <asm/unistd.h> __syscall_return
macro which is used by the _syscallX macros set the errno variable - even
inside the kernel. In the age of SMP this looks broken - at least nothing
seems to rely on it. So how about removing the whole errno thing from
there?
Ralf
next prev parent reply other threads:[~2000-06-25 21:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <NDBBIDGAOKMNJNDAHDDMCEODCKAA.mfklar@ponymail.com>
[not found] ` <u8d7l6p0vq.fsf@gromit.rhein-neckar.de>
2000-06-25 18:43 ` errno assignment in _syscall macros and glibc Ralf Baechle
2000-06-25 18:53 ` Andreas Jaeger
2000-06-25 21:59 ` Ralf Baechle
2000-06-25 19:26 ` Alan Cox
2000-06-25 19:26 ` Alan Cox
2000-06-25 21:21 ` Ralf Baechle
2000-06-25 21:25 ` Alan Cox
2000-06-25 21:25 ` Alan Cox
2000-06-25 21:48 ` Ralf Baechle [this message]
2000-06-30 14:03 ` Jay Carlson
2000-06-30 14:03 ` Jay Carlson
2000-07-03 13:45 ` Alan Cox
2000-07-03 13:45 ` Alan Cox
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=20000625234833.B3802@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=aj@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-mips@fnet.fr \
--cc=linux-mips@oss.sgi.com \
--cc=linux-mips@vger.rutgers.edu \
--cc=mfklar@ponymail.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 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.