From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11311 invoked by alias); 17 Jul 2007 11:00:35 -0000 Received: (qmail 11283 invoked by uid 48); 17 Jul 2007 11:00:25 -0000 Date: Tue, 17 Jul 2007 11:00:00 -0000 Message-ID: <20070717110025.11282.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/msg01846.txt.bz2 ------- Comment #6 from jensseidel at users dot sf dot net 2007-07-17 11:00 ------- (In reply to comment #4) > grpof profiling is all done via a call to mcount and mcount is controlled by > libc (in the GNU/Linux case glibc). So I doubt this is a GCC bug.> OK, for the record: I use OpenSuse 10.2 with glibc 2.5. According to http://www.cs.utah.edu/dept/old/texinfo/as/gprof.html#SEC1 mcount occurs in the gprof output but I haven't seen this yet (gprof 2.17.50.0.5). (In reply to comment #5) > And that is the reason why GCC added atomic builtins when openmp came > in also. There are manuals for a reason :). I don't understand this but it may be off topic. (Should I inform the Open MPI people about atomic assembler locking code in gcc so that they can reuse it?) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32789