Converse command line arguments produce false warnings
Converse command line arguments are not properly registered during initialization, so using them generates a warning that they are not being parsed by the runtime.
The command line options in convcore.c are +csdLocalMax, +useAbsoluteTime, +nice, +CmiSpinOnIdle, +CmiSleepOnIdle, and +CmiNoProcForComThread.
#2 Updated by Eric Mikida almost 3 years ago
There are two separate issues here from what I can tell.
For +nice and +csdLocalMax, they are correctly registered and function fine. The warning prints out when you pass them without an integer argument since they are registered as integer command line options. So here, I think either the general warning needs to be clarified to say that the option may not have been used as intended, or if we try to consume a command line argument that does is not used properly we should spit out an error right then and there. I would lean towards the latter.
For the others, they never seem to be read from the command line (at least for the build im currently using which is netlrts-linux-x86_64). I need to dig a bit further to figure out when and where they are used and therefore where they should be registered to the CLA database.
#3 Updated by Eric Mikida almost 3 years ago
+useAbsoluteTime, +CmiSpinOnIdle, +CmiSleepOnIdle, and +CmiNoProcForComThread are all SMP options, and when running with the SMP build the warning does not show up as expected.
In summary, all of the above options seem to be registered correctly, and the warning functions as expected. The only thing that should change is that if an option that expects an int isn't given an int, there should be an error. I'm pretty sure that the Charm++ options do something like that, so the same functionality should be added for Converse options. I'll look to add that some time this week probably.