<html>
<head>
<base href="https://llvm.org/bugs/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:jonathan.sauer@gmx.de" title="jonathan.sauer@gmx.de">jonathan.sauer@gmx.de</a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED INVALID - int32_t vs. int64_t vs. long ambiguity"
href="https://llvm.org/bugs/show_bug.cgi?id=23404">bug 23404</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;">Status</td>
<td>NEW
</td>
<td>RESOLVED
</td>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>jonathan.sauer@gmx.de
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>INVALID
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED INVALID - int32_t vs. int64_t vs. long ambiguity"
href="https://llvm.org/bugs/show_bug.cgi?id=23404#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED INVALID - int32_t vs. int64_t vs. long ambiguity"
href="https://llvm.org/bugs/show_bug.cgi?id=23404">bug 23404</a>
from <span class="vcard"><a class="email" href="mailto:jonathan.sauer@gmx.de" title="jonathan.sauer@gmx.de">jonathan.sauer@gmx.de</a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=23404#c0">comment #0</a>)
<span class="quote">> Is there a reason why a 64-bit 'long' value cannot unambiguously match
> std::int64_t?</span >
When std::int64_t is defined as long long, the compiler cannot decide between
"foo(int)" and "foo(long long)". Use the macro INT64_C to create a constant of
type std::int64_t, e.g.
INT64_C(123)
I'm closing this report because I don't think it's a bug. Please feel free to
reopen if you disagree.</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>