This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libgomp/58642] gomp regression: not "honoring" anymore task set and numactl
- From: "jakub at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 07 Oct 2013 12:16:41 +0000
- Subject: [Bug libgomp/58642] gomp regression: not "honoring" anymore task set and numactl
- Auto-submitted: auto-generated
- References: <bug-58642-4 at http dot gcc dot gnu dot org/bugzilla/>
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.