likwid-pin: Wild core IDs when # of threads too large

[GoogleCodeExporter]

$ unrz55@e0549:~/projects/stream$ likwid-pin -c E:N:40:1:2 ./stream_omp_NT.exe 

one one 2xten-core Ivy Bridge node with SMT enabled yields the 
following diagnostic output:

-- SNIP --
        threadid 47278207280896 -> core 15 - OK
        threadid 47278211479296 -> core 16 - OK
        threadid 47278534428416 -> core 17 - OK
        threadid 47278538626816 -> core 18 - OK
        threadid 47278542825216 -> core 19 - OK
        threadid 47278735755008 -> core 32 - OK
        threadid 47278739953408 -> core 33 - OK
        threadid 47278937081600 -> core 18 - OK
        threadid 47278941280000 -> core 25140608 - OK
        threadid 47278945478400 -> core 32 - OK
        threadid 47279138408192 -> core 33 - OK
        threadid 47279406843648 -> core -1064566706 - OK
        threadid 47279339734784 -> core -1064513832 - OK
        threadid 47279343933184 -> core 0 - OK
        threadid 47279348131584 -> core 97 - OK
        threadid 47279352329984 -> core 0 - OK
        threadid 47279356528384 -> core 1 - OK
        threadid 47279411042048 -> core 2 - OK
        threadid 47279415240448 -> core 3 - OK
        threadid 47279419438848 -> core 4 - OK
        threadid 47279423637248 -> core 5 - OK
        threadid 47279427835648 -> core 6 - OK
        threadid 47279432034048 -> core 7 - OK
        threadid 47279436232448 -> core 8 - OK
        threadid 47279440430848 -> core 9 - OK
 Number of Threads =           40

Hence, bogus thread IDs are used to pin the excess threads. 

likwid-3.1

Original issue reported on code.google.com by hager.ge...@gmail.com on 15 May 2014 at 8:45

[GoogleCodeExporter]

This issue was closed by revision c0d82a2aefd0.

Original comment by Thomas.R...@googlemail.com on 15 May 2014 at 11:24

• Changed state: Fixed

[GoogleCodeExporter]

This issue was closed by revision 04fd1429c94a.

Original comment by Thomas.R...@googlemail.com on 15 May 2014 at 11:28

[GoogleCodeExporter]

This issue was closed by revision 66269b2cb376.

Original comment by Thomas.R...@googlemail.com on 16 May 2014 at 10:14