public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jk3064 at arcor dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/55411] OMP threads lose their OMP_WAIT_POLICY when another OMP thread gets destructed
Date: Sun, 02 Dec 2012 17:26:00 -0000	[thread overview]
Message-ID: <bug-55411-4-TffFPHU6Nk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55411-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55411

jk3064 <jk3064 at arcor dot de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED

--- Comment #7 from jk3064 <jk3064 at arcor dot de> 2012-12-02 17:26:14 UTC ---
Thank you!
That fixed it.
The omp threads of the 2nd thread obv. still don't copy the policies of the
main one, but this would be even counterproductive (you would have ~twice more
threads with 100% cpu usage than you got cores). This could only be solved with
an either process or OS shared workerpool, what is another topic. So the ticket
can be closed :)


      parent reply	other threads:[~2012-12-02 17:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-20 10:03 [Bug libgomp/55411] New: " jk3064 at arcor dot de
2012-11-20 10:04 ` [Bug libgomp/55411] " jk3064 at arcor dot de
2012-11-21  2:14 ` pinskia at gcc dot gnu.org
2012-11-21  3:20 ` jk3064 at arcor dot de
2012-11-21 10:31 ` jakub at gcc dot gnu.org
2012-11-21 20:30 ` jakub at gcc dot gnu.org
2012-11-21 20:32 ` jakub at gcc dot gnu.org
2012-12-02 17:26 ` jk3064 at arcor dot de [this message]

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-55411-4-TffFPHU6Nk@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: 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).