<html>
<head>
<base href="https://bugs.llvm.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:richard-llvm@metafoo.co.uk" title="Richard Smith <richard-llvm@metafoo.co.uk>"> <span class="fn">Richard Smith</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED DUPLICATE - Supposedly-incorrect error 'constexpr variable... must be initialized by a constant expression'"
href="https://bugs.llvm.org/show_bug.cgi?id=36333">bug 36333</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>DUPLICATE
</td>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEW
</td>
<td>RESOLVED
</td>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>richard-llvm@metafoo.co.uk, tstellar@redhat.com
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED DUPLICATE - Supposedly-incorrect error 'constexpr variable... must be initialized by a constant expression'"
href="https://bugs.llvm.org/show_bug.cgi?id=36333#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED DUPLICATE - Supposedly-incorrect error 'constexpr variable... must be initialized by a constant expression'"
href="https://bugs.llvm.org/show_bug.cgi?id=36333">bug 36333</a>
from <span class="vcard"><a class="email" href="mailto:richard-llvm@metafoo.co.uk" title="Richard Smith <richard-llvm@metafoo.co.uk>"> <span class="fn">Richard Smith</span></a>
</span></b>
<pre>Reduced: <a href="https://godbolt.org/g/DwtMmM">https://godbolt.org/g/DwtMmM</a>
struct ObfDescriptor {
constexpr ObfDescriptor(int n) : n(n) {}
int n;
};
struct Arr { ObfDescriptor od[1]; };
template<int Dependent> struct obf_str_literal {
static constexpr int sz4 = Dependent;
constexpr static Arr split = {ObfDescriptor(sz4)};
};
This is the same as <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - Reproducible Clang crash + strongly suspected invalid code generation"
href="show_bug.cgi?id=36055">bug#36055</a>.
(In reply to Sergey Ignatchenko from <a href="show_bug.cgi?id=36333#c0">comment #0</a>)
<span class="quote">> NB: it MIGHT be a different manifestation of recently-fixed <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - Reproducible Clang crash + strongly suspected invalid code generation"
href="show_bug.cgi?id=36055">bug #36055</a>, but
> if so - it would be nice to re-apply the fix back to Clang 5.0.x (which is
> still the-latest-greatest-officially-released-Clang). </span >
Clang 6 (in which this is fixed) will be released soon. We have historically
not done point releases for older releases after a new release is shipped.
+Tom Stellard, though, in case we do choose to release a Clang 5.0.2.
*** This bug has been marked as a duplicate of <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - Reproducible Clang crash + strongly suspected invalid code generation"
href="show_bug.cgi?id=36055">bug 36055</a> ***</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>