public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "steven at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug gcov-profile/28441] Need atomic increment of gcov counters for MP programs Date: Sat, 21 Jul 2012 23:26:00 -0000 [thread overview] Message-ID: <bug-28441-4-gmmNRwcwFH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-28441-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28441 Steven Bosscher <steven at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |matz at gcc dot gnu.org, | |rguenth at gcc dot gnu.org, | |steven at gcc dot gnu.org --- Comment #15 from Steven Bosscher <steven at gcc dot gnu.org> 2012-07-21 23:25:38 UTC --- Matz's patch http://gcc.gnu.org/ml/gcc-patches/2007-03/msg00950.html was never committed on the trunk. That's unfortunate, we're living more and more in a multi-threaded world. Also, the atomic operations in GCC 4.8 should make this easier to implement for all targets now (instead of only for i386). Matz, could you have a look and see if you're interested in finishing that nice piece of work of yours? Or if you're not interested, let that know, too, so someone else can pick up the ball where you drop it! :-)
next parent reply other threads:[~2012-07-21 23:26 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-28441-4@http.gcc.gnu.org/bugzilla/> 2012-07-21 23:26 ` steven at gcc dot gnu.org [this message] 2006-07-20 0:47 [Bug gcov/profile/28441] New: " gnb at sgi dot com 2006-12-06 20:50 ` [Bug gcov-profile/28441] " gnb at melbourne dot sgi dot com 2007-01-10 1:25 ` gnb at melbourne dot sgi dot com 2007-03-14 23:03 ` hubicka at gcc dot gnu dot org 2008-08-22 18:18 ` pinskia at gcc dot gnu dot 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=bug-28441-4-gmmNRwcwFH@http.gcc.gnu.org/bugzilla/ \ --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: linkBe 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).