Current parsing allows trailing string after the permitted value MANDATORY|DISABLED|DEFAULT -- e.g., mandatorynot is also recognized as MANDATORY.
Such cases should be recognized as incorrect/unknown value.
Details
Details
Diff Detail
Diff Detail
- Repository
- rOMP OpenMP
Event Timeline
Comment Actions
looks like a good change
also consistent with some recent OpenMP language examples committee discussions on this topic.
Comment Actions
Probably test case worth adding. Or even two, - one negative with something like "mandatorynot" value, another positive (we do have internal getter routine for the target-offload-var ICV).
Comment Actions
By negative test I meant the wrong value is ignored and the default used instead. I don't think we need to check library warnings.
Comment Actions
Yes, I agree that it is good to have tests for this -- I will be updating the patch with tests.