From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32383 invoked by alias); 17 Jul 2007 10:24:23 -0000 Received: (qmail 32323 invoked by uid 48); 17 Jul 2007 10:24:12 -0000 Date: Tue, 17 Jul 2007 10:24:00 -0000 Message-ID: <20070717102412.32322.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug libgomp/32789] Profiling not possible with -fopenmp In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "jensseidel at users dot sf dot net" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2007-07/txt/msg01839.txt.bz2 ------- Comment #3 from jensseidel at users dot sf dot net 2007-07-17 10:24 ------- (In reply to comment #2) > And to reply to myself, it needs either to use thread local storage to hold the > counters and then to add some piece of code to fuse the values of the various > counters at the end of a thread (which might not be easy ?) or to use atomic > operations (which existence depends on the architecture, but I hope that all > multi-core processors have such instructions). (Don't forget about SMP machines, I have a SGI Octane (2 x Mips R12000 CPUs).) An Open MPI related discussion about atomic operations happened the last days, because architecture specific assembler code failed again for some exotic platforms. See e.g. http://lists.debian.org/debian-mips/2007/07/msg00036.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32789