Article View: gnu.gcc.help
Article #51567Re: threads, gcc and sunOS
From: Joe Korty
Date: Tue, 04 May 1993 17:12
Date: Tue, 04 May 1993 17:12
25 lines
1608 bytes
1608 bytes
In <1993May3.171615.25882@spectrum.xerox.com> leisner@wrc.xerox.com (Marty Leisner x71348 ) writes: >In the '92 Summer Usenix paper "Implementing Lightweight Threads" >by D. Stein and D. Shah and SunSoft, they talked about a >pragma in the C compiler to communication thread private >data... >This is necessary if each thread gets its own copy of errno... >How (or does) gcc plan on getting around the problem? There are many ways to implement threads without making compiler changes. For example, the errno problem can be handled by making errno a macro which expands to the code necessary to fetch and/or modify the thread-specific errno value. The POSIX 1003.4 thread draft (or standard?, I haven't been following it lately) would be a good place to start looking for ideas on this subject. -- Joe Korty, REAL/IX Operating Systems MODCOMP, an AEG Company Telephone: (305) 977-1820 1650 West McNab Road Fax: (305) 977-1638 P.O. Box 6099 E-mail: uunet!modcomp!joe Ft. Lauderdale, FL 33309-1088
Technical Details
Message-ID:
<joe.736535562@rlxdev>Path:
arc1-ca.pugleaf.net!gmd.de!Germany.EU.net!mcsun!news.funet.fi!news.tele.fi!uunet!modcomp!joeReferences:
<1993May3.171615.25882@spectrum.xerox.com>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 11318c,ea0d529a8356594c X-Google-Attributes: gid11318c,public X-Google-ArrivalTime: 1993-05-04 22:20:33 PST Newsgroups: gnu.gcc.help Path: arc1-ca.pugleaf.net!gmd.de!Germany.EU.net!mcsun!news.funet.fi!news.tele.fi!uunet!modcomp!joe From: joe@modcomp.uucp (Joe Korty) Subject: Re: threads, gcc and sunOS Organization: MODCOMP, an AEG company Date: Tue, 4 May 1993 17:12:42 GMT Message-ID: <joe.736535562@rlxdev> References: <1993May3.171615.25882@spectrum.xerox.com> Sender: news@modcomp.uucp (Mr. News) Lines: 25