public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jensseidel at users dot sf dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/32789] Profiling not possible with -fopenmp
Date: Tue, 17 Jul 2007 10:24:00 -0000	[thread overview]
Message-ID: <20070717102412.32322.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32789-14868@http.gcc.gnu.org/bugzilla/>



------- 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


  parent reply	other threads:[~2007-07-17 10:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-17  8:49 [Bug libgomp/32789] New: " jensseidel at users dot sf dot net
2007-07-17  9:55 ` [Bug libgomp/32789] " theodore dot papadopoulo at sophia dot inria dot fr
2007-07-17 10:11 ` theodore dot papadopoulo at sophia dot inria dot fr
2007-07-17 10:24 ` jensseidel at users dot sf dot net [this message]
2007-07-17 10:26   ` Andrew Pinski
2007-07-17 10:24 ` pinskia at gcc dot gnu dot org
2007-07-17 10:27 ` pinskia at gmail dot com
2007-07-17 11:00 ` jensseidel at users dot sf dot net
     [not found] <bug-32789-4@http.gcc.gnu.org/bugzilla/>
2021-12-29  7:19 ` pinskia at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070717102412.32322.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).