public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vincenzo.innocente at cern dot ch" <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: Mon, 07 Oct 2013 12:43:00 -0000 [thread overview] Message-ID: <bug-58642-4-wocjrrWLfY@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 #24 from vincenzo Innocente <vincenzo.innocente at cern dot ch> --- ok, modified to ">=" taskset -c 0-31 gdb ./affinity-1.exe GNU gdb (GDB) Red Hat Enterprise Linux (7.2-60.el6_4.1) (gdb) b /home/data/newsoft/gcc-gomp4/libgomp/testsuite/libgomp.c/affinity-1.c:179 Breakpoint 1 at 0x400d5f: file /home/data/newsoft/gcc-gomp4/libgomp/testsuite/libgomp.c/affinity-1.c, line 179. (gdb) run Breakpoint 1, main () at /home/data/newsoft/gcc-gomp4/libgomp/testsuite/libgomp.c/affinity-1.c:181 181 /home/data/newsoft/gcc-gomp4/libgomp/testsuite/libgomp.c/affinity-1.c: No such file or directory. in /home/data/newsoft/gcc-gomp4/libgomp/testsuite/libgomp.c/affinity-1.c Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.107.el6_4.4.x86_64 (gdb) print contig_cpucount $1 = 32 and then spawn etc but taskset -c 24-31 gdb ./affinity-1.exe Breakpoint 1, main () at /home/data/newsoft/gcc-gomp4/libgomp/testsuite/libgomp.c/affinity-1.c:181 181 /home/data/newsoft/gcc-gomp4/libgomp/testsuite/libgomp.c/affinity-1.c: No such file or directory. in /home/data/newsoft/gcc-gomp4/libgomp/testsuite/libgomp.c/affinity-1.c Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.107.el6_4.4.x86_64 (gdb) print contig_cpucount $1 = 0 I see anyhow where contig_cpucount is set. up to you to generalize the test… v. On 7 Oct, 2013, at 2:16 PM, jakub at gcc dot gnu.org <gcc-bugzilla@gcc.gnu.org> wrote: > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58642 > > --- Comment #23 from Jakub Jelinek <jakub at gcc dot gnu.org> --- > Ah, right, obviously I meant > --- libgomp/testsuite/libgomp.c/affinity-1.c 2013-10-07 09:31:53.884695701 > +0200 > +++ libgomp/testsuite/libgomp.c/affinity-1.c 2013-10-07 14:09:52.475331358 > +0200 > @@ -178,7 +178,7 @@ main () > int test_places = 0; > > #ifdef DO_FORK > - if (env_places == NULL && contig_cpucount == 8 && test_false > + if (env_places == NULL && contig_cpucount >= 8 && test_false > && getenv ("GOMP_AFFINITY") == NULL) > { > int i, j, status; > (the other spot already correctly uses >= 8 - all the testcase cares about is > that the first 8 logical CPUs can be used for affinity). > That answers the not seeing fork case, but if it doesn't print any verified > lines even with that, there would be some other issue. > > -- > You are receiving this mail because: > You reported the bug. -- Il est bon de suivre sa pente, pourvu que ce soit en montant. A.G. http://www.flickr.com/photos/vin60/1320965757/ >From gcc-bugs-return-431258-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Oct 07 13:02:25 2013 Return-Path: <gcc-bugs-return-431258-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 773 invoked by alias); 7 Oct 2013 13:02:24 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 737 invoked by uid 48); 7 Oct 2013 13:02:22 -0000 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: Mon, 07 Oct 2013 13:02:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libgomp X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-58642-4-KrBY9KzspN@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-58642-4@http.gcc.gnu.org/bugzilla/> References: <bug-58642-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2013-10/txt/msg00402.txt.bz2 Content-length: 356 http://gcc.gnu.org/bugzilla/show_bug.cgi?idX642 --- Comment #25 from Jakub Jelinek <jakub at gcc dot gnu.org> --- It is fine if the testcase doesn't fork and doesn't verify for taskset -c 24-31, that would be too hard to support, the testcase doesn't fail because of that. But, do you get the ", verified" strings in the lines for taskset -c 0-31 run?
next prev parent reply other threads:[~2013-10-07 12:43 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 ` [Bug libgomp/58642] " jakub at gcc dot gnu.org 2013-10-06 14:05 ` 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 [this message] 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-wocjrrWLfY@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).