From: Jeffrey A Law <law@cygnus.com>
To: mrs@wrs.com (Mike Stump)
Cc: egcs@cygnus.com, wilson@cygnus.com
Subject: Re: Thread support for VxWorks
Date: Fri, 03 Apr 1998 21:52:00 -0000 [thread overview]
Message-ID: <5557.891587734@hurl.cygnus.com> (raw)
In-Reply-To: <199802052340.PAA23288@kankakee.wrs.com>
In message <199802052340.PAA23288@kankakee.wrs.com>you write:
> Here is a first cut at thread support for C++ EH. I noticed that the
> FSF doesn't have thread support yet, does someone want to work on
> getting all the threading work into the FSF tree?
>
> 1998-02-05 Mike Stump <mrs@wrs.com>
>
> * gthr.h: Support systems that don't have weak, but have threads.
> * configure.in (*wrs-vxworks*): Use VxWorks threads by default.
> * gthr-vxworks.h: New file.
> * objc/thr-vxworks.h: Dummy file from thr-single.c for now.
Nobody seemed to want to comment on this patch. I don't see that
it'll break anything but possibly VxWorks. I went ahead and installed
it.
If it causes any problems we'll just have to deal with them.
jeff
next prev parent reply other threads:[~1998-04-03 21:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-05 17:44 Mike Stump
1998-04-03 21:52 ` Jeffrey A Law [this message]
1998-04-03 21:52 Mike Stump
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=5557.891587734@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=egcs@cygnus.com \
--cc=mrs@wrs.com \
--cc=wilson@cygnus.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).