From: "Alec Voropay" <a.voropay@vmb-service.ru>
To: "'Ralf Baechle'" <ralf@linux-mips.org>
Cc: <linux-mips@linux-mips.org>
Subject: RE: anybody tried NPTL?
Date: Mon, 23 Aug 2004 19:09:31 +0400 [thread overview]
Message-ID: <036001c48923$31563350$1701a8c0@alec> (raw)
In-Reply-To: <20040823122843.GB20905@linux-mips.org>
Ralf Baechle [mailto:ralf@linux-mips.org] wrote:
> In addition to what Dom has already answered - there are very
> significant differences between the multithreading as
> implemented in the Windows OS family and the varioius
> threading implementations for Linux like classic
> libpthreads, Linuxthreads, NPTL, Mozilla and more.
> If we legally could look at MS's code I'd not expect to find
> much useful for us there ...
OK, OK. You are right. However, as it is known, there is at
least one project "to bridge" Win32/multithread and *NIX :
WINE.
http://winehq.com/site/docs/wine-devel/x3398
Yes, the Win32/MIPS API (and ABI) is dead, but MIPS/multithreading
lives in the WindowsCE/MIPS HPCs.
Unfortunately, I can't find any details about Win32/MIPS
implementation.
--
-=VA=-
WARNING: multiple messages have this Message-ID (diff)
From: "Alec Voropay" <a.voropay@vmb-service.ru>
To: 'Ralf Baechle' <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: RE: anybody tried NPTL?
Date: Mon, 23 Aug 2004 19:09:31 +0400 [thread overview]
Message-ID: <036001c48923$31563350$1701a8c0@alec> (raw)
Message-ID: <20040823150931.1Ikkbtfk5gn7VZYdL-pyo6-21sa_iFd7Ki6yEyYGLyg@z> (raw)
In-Reply-To: <20040823122843.GB20905@linux-mips.org>
Ralf Baechle [mailto:ralf@linux-mips.org] wrote:
> In addition to what Dom has already answered - there are very
> significant differences between the multithreading as
> implemented in the Windows OS family and the varioius
> threading implementations for Linux like classic
> libpthreads, Linuxthreads, NPTL, Mozilla and more.
> If we legally could look at MS's code I'd not expect to find
> much useful for us there ...
OK, OK. You are right. However, as it is known, there is at
least one project "to bridge" Win32/multithread and *NIX :
WINE.
http://winehq.com/site/docs/wine-devel/x3398
Yes, the Win32/MIPS API (and ABI) is dead, but MIPS/multithreading
lives in the WindowsCE/MIPS HPCs.
Unfortunately, I can't find any details about Win32/MIPS
implementation.
--
-=VA=-
next prev parent reply other threads:[~2004-08-23 15:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-04 22:29 anybody tried NPTL? Jun Sun
2004-08-05 1:08 ` Kumba
2004-08-05 17:14 ` Jun Sun
2004-08-06 2:03 ` Ralf Baechle
2004-08-19 14:17 ` Dominic Sweetman
2004-08-19 14:31 ` Alec Voropay
2004-08-19 14:31 ` Alec Voropay
2004-08-20 6:07 ` Dominic Sweetman
2004-08-20 6:07 ` Dominic Sweetman
2004-08-23 12:28 ` Ralf Baechle
2004-08-23 15:09 ` Alec Voropay [this message]
2004-08-23 15:09 ` Alec Voropay
2004-08-23 17:19 ` Ralf Baechle
2004-08-19 16:01 ` David Daney
2004-08-20 6:19 ` Dominic Sweetman
2004-08-19 22:16 ` Jun Sun
2004-08-20 13:46 ` Dominic Sweetman
2004-08-23 13:28 ` Daniel Jacobowitz
2004-08-23 17:12 ` Ralf Baechle
2004-08-23 17:44 ` Daniel Jacobowitz
2004-08-23 19:13 ` Ralf Baechle
2004-08-23 17:37 ` Jun Sun
2004-08-23 19:25 ` Ralf Baechle
2004-08-20 13:12 ` Thiemo Seufer
2004-08-20 16:52 ` Dominic Sweetman
2004-09-01 9:17 ` Richard Sandiford
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='036001c48923$31563350$1701a8c0@alec' \
--to=a.voropay@vmb-service.ru \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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.