public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/58642] gomp regression: not "honoring" anymore task set and numactl
Date: Sun, 06 Oct 2013 13:56:00 -0000	[thread overview]
Message-ID: <bug-58642-4-vOAfVdctAM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58642-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Weird, can't reproduce.
/tmp/ttt
8
taskset -c 0-3 /tmp/ttt
4
ldd /tmp/ttt | grep libgomp
    libgomp.so.1 =>
/usr/src/gomp-4.0/obj/x86_64-unknown-linux-gnu/libgomp/.libs/libgomp.so.1
(0x00007fda5e2e8000)
strace /tmp/ttt 2>&1 | grep affinity
sched_getaffinity(30384, 8, {ff})       = 8
taskset -c 0-3 strace /tmp/ttt 2>&1 | grep affinity
sched_getaffinity(30389, 8, {f})        = 8

Do you have the default linux build (i.e. --enable-linux-futex), or one without
that (that doesn't honor affinity)?


  reply	other threads:[~2013-10-06 13:56 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-06 13:42 [Bug libgomp/58642] New: " vincenzo.innocente at cern dot ch
2013-10-06 13:56 ` jakub at gcc dot gnu.org [this message]
2013-10-06 14:05 ` [Bug libgomp/58642] " jakub at gcc dot gnu.org
2013-10-06 14:38 ` vincenzo.innocente at cern dot ch
2013-10-06 15:15 ` vincenzo.innocente at cern dot ch
2013-10-06 18:02 ` jakub at gcc dot gnu.org
2013-10-06 19:31 ` jakub at gcc dot gnu.org
2013-10-07  6:49 ` vincenzo.innocente at cern dot ch
2013-10-07  6:53 ` vincenzo.innocente at cern dot ch
2013-10-07  7:47 ` jakub at gcc dot gnu.org
2013-10-07  7:58 ` vincenzo.innocente at cern dot ch
2013-10-07  8:04 ` jakub at gcc dot gnu.org
2013-10-07  8:06 ` jakub at gcc dot gnu.org
2013-10-07  8:08 ` vincenzo.innocente at cern dot ch
2013-10-07  8:12 ` vincenzo.innocente at cern dot ch
2013-10-07 10:14 ` vincenzo.innocente at cern dot ch
2013-10-07 10:28 ` jakub at gcc dot gnu.org
2013-10-07 11:03 ` vincenzo.innocente at cern dot ch
2013-10-07 11:06 ` vincenzo.innocente at cern dot ch
2013-10-07 11:32 ` jakub at gcc dot gnu.org
2013-10-07 11:39 ` jakub at gcc dot gnu.org
2013-10-07 12:07 ` vincenzo.innocente at cern dot ch
2013-10-07 12:43 ` vincenzo.innocente at cern dot ch
2013-10-07 13:22 ` vincenzo.innocente at cern dot ch
2013-10-07 17:04 ` jakub at gcc dot gnu.org
2013-10-08  6:40 ` vincenzo.innocente at cern dot ch
2013-10-08  7:22 ` vincenzo.innocente at cern dot ch
2013-10-11 10:40 ` jakub 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=bug-58642-4-vOAfVdctAM@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).