Not-so-pretty fix for logical numbering output. Needs improvement

[GuillaumeMercier]

No description provided.

[samuelkgutierrez]

Thank you, @GuillaumeMercier.

I'm a little worried about the length of the logical listing. For example, I see the following while running test-process-scopes:

Current cpubind is 0-5 | cpubind (logical)=[0,1,2,3,4,5]

On my machine the string isn't excessively long, but I fear for high core count machines the logical list will be. How much of a pain would it be for the logical and physical outputs to be the same format? For example,

Current cpubind is 0-5 | cpubind (logical)=0-5

Will the logical output change to a bitmap listing when we ask for the bitmap format?

[GuillaumeMercier]

@samuelkgutierrez : I took a look at the code in hwloc and it seemed rather painful to get the result you want (and that I'd like to have too). But I think that I'll give it a shot. meanwhile, I pushed another version where I compute the strings lengths so that there won't be any size issue w.r.t this matter.

[GuillaumeMercier]

Will the logical output change to a bitmap listing when we ask for the bitmap format?

No, right now, it's the same output. I don't think that it would make any sense to have a bitmap format for logical indices anyway.
BTW, it would be nice to have the same compilation flags between the git repo and the CI here. My code compiles just fine on my system but fails failed here because there are issues trigered by the flag -Werror=stringop-overflow=.

[GuillaumeMercier]

On my machine the string isn't excessively long, but I fear for high core count machines the logical list will be. How much of a pain would it be for the logical and physical outputs to be the same format?

Done.

Will the logical output change to a bitmap listing when we ask for the bitmap format?

I discussed about this with Brice and we agreed that it would be very confusing and it should be avoided.

[samuelkgutierrez]

Thank you, @GuillaumeMercier.

[samuelkgutierrez]

Fixes #286.