Related articles |
---|
Instrumenting multithreaded applications legendre@u.arizona.edu (Matthew Legendre) (2003-01-21) |
Re: Instrumenting multithreaded applications nmm1@cus.cam.ac.uk (2003-01-25) |
Re: Instrumenting multithreaded applications mailbox@dmitry-kazakov.de (Dmitry A.Kazakov) (2003-01-25) |
Re: Instrumenting multithreaded applications jstracke@speakeasy.net (John Stracke) (2003-01-25) |
Re: Instrumenting multithreaded applications bobduff@World.std.com (Robert A Duff) (2003-01-25) |
Re: Instrumenting multithreaded applications bje@redhat.com (Ben Elliston) (2003-01-25) |
Re: Instrumenting multithreaded applications joachim_d@gmx.de (Joachim Durchholz) (2003-01-25) |
Re: Instrumenting multithreaded applications chase@world.std.com (David Chase) (2003-01-25) |
Re: Instrumenting multithreaded applications lex@cc.gatech.edu (Lex Spoon) (2003-01-25) |
Re: Instrumenting multithreaded applications idbaxter@semdesigns.com (Ira Baxter) (2003-01-26) |
From: | Ben Elliston <bje@redhat.com> |
Newsgroups: | comp.compilers |
Date: | 25 Jan 2003 01:00:35 -0500 |
Organization: | Red Hat Asia-Pacific Pty Ltd |
References: | 03-01-118 |
Keywords: | parallel, testing |
Posted-Date: | 25 Jan 2003 01:00:32 EST |
>>>>> "Matthew" == Matthew Legendre <legendre@u.arizona.edu> writes:
> We've got a situation where we want to insert instrumentation into a
> multithreaded application (for profiling purposes). We need to use
> some form of mutual exclusion since the instrumentation writes to a
> global data structure.
If you wish to instrument each thread, why not use thread local
storage to store the instrumentation data? That way, you should not
require any thread synchronisation.
Ben
Return to the
comp.compilers page.
Search the
comp.compilers archives again.