The defintion is not part of the spec and thus should not have the prefix "ompt_" but rather a prefix that indicates that this is implementation specific.
Details
Details
Diff Detail
Diff Detail
- Repository
- rL LLVM
Event Timeline
Comment Actions
Makes sense in some way. However if I read the spec correctly the tool gets an unsigned int. So maybe we should keep the enum in the header but prefix it with kmp instead of ompt to make clear that this is not portable? This would allow tools to conditionally compare the passed value
runtime/src/include/50/ompt.h.var | ||
---|---|---|
87 ↗ | (On Diff #127842) | This is actually defined in the spec, so we need to keep it prefixed with ompt |
runtime/src/include/50/ompt.h.var | ||
---|---|---|
87 ↗ | (On Diff #127842) | You're right. The spec specifies this value as a macro however (not an enum). I think we should wait for feedback on Github Issue 112 |
Comment Actions
We discussed to relax the wording in the OpenMP spec, so that any implementation that provides ompt_mutex_impl_unknown with value 0 is complying. This will include #define, enum or "static const" values.