This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Thread support in GCC
- From: "Leif Ekblad" <leif at rdos dot net>
- To: <gcc at gcc dot gnu dot org>
- Date: Thu, 19 Jan 2006 13:18:23 +0100
- Subject: Thread support in GCC
- References: <20051229083827.56B6384025@ws1-5.us4.outblaze.com> <69F191C3-9B76-4FBB-A8BE-EE0CF8F09A09@apple.com> <046001c60cb0$5fdf87a0$0201a8c0@LEIFACER> <40FF9C62-30CD-4703-80EF-2453A415A454@apple.com> <04a701c60cbb$12b99e10$0201a8c0@LEIFACER> <13AB625C-8D2E-496A-B88C-C13B767B3BBD@apple.com> <00f201c6169f$a34e8100$410aa8c0@codab.home> <00de01c61762$3d386de0$410aa8c0@codab.home>
- Reply-to: leif at rdos dot net
I've localized the supporting module in GCC for
threads (gthr.h and gthr-xxx.h). These primitives
seems fairly easy to support, but there seems to
be a major flaw in them. While there is an initialization
macro, there is no descruction macro. This is problematic
when these functions need to allocate kernel reasources,
that must eventually be reclaimed. It is no problem
to free these up on termination, but if they build up
during execution, it would be problematic.
Are these objects created at load time and kept
for the duration of the run or are they sometimes
allocated and reallocated?
Leif Ekblad
www.rdos.net/rdos