<html>
<head>
<base href="https://bugs.llvm.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - OpenMP version printed for OMP_DISPLAY_ENV=1"
href="https://bugs.llvm.org/show_bug.cgi?id=49880">49880</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>OpenMP version printed for OMP_DISPLAY_ENV=1
</td>
</tr>
<tr>
<th>Product</th>
<td>OpenMP
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>PC
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>enhancement
</td>
</tr>
<tr>
<th>Priority</th>
<td>P
</td>
</tr>
<tr>
<th>Component</th>
<td>Runtime Library
</td>
</tr>
<tr>
<th>Assignee</th>
<td>unassignedbugs@nondot.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>protze@itc.rwth-aachen.de
</td>
</tr>
<tr>
<th>CC</th>
<td>llvm-bugs@lists.llvm.org
</td>
</tr></table>
<p>
<div>
<pre>Currently, the runtime prints _OPENMP='201611', when exporting
OMP_DISPLAY_ENV=1.
This is other than the value of _OPENMP=201811 during compilation.
Furthermore, 201611 is not a value defined in any spec.
As LC members would argue, an OpenMP implementation should always be seen as a
fixed combination of compiler and runtime. Such implementation should report a
consistent version (at least for the default usage).
Cases, where mileage might vary:
- flag -fopenmp-version=xy is passed to compiler -> compile-time value of
_OPENMP changes
- different compiler than clang is used while linking against libomp
- clang-compiled application/library is linked against a different OpenMP
runtime.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>