[LLVMbugs] [Bug 23404] int32_t vs. int64_t vs. long ambiguity

bugzilla-daemon at llvm.org bugzilla-daemon at llvm.org
Mon May 4 02:36:55 PDT 2015


jonathan.sauer at gmx.de changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
                 CC|                            |jonathan.sauer at gmx.de
         Resolution|---                         |INVALID

--- Comment #1 from jonathan.sauer at gmx.de ---
(In reply to comment #0)
> Is there a reason why a 64-bit 'long' value cannot unambiguously match
> std::int64_t?

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.


I'm closing this report because I don't think it's a bug. Please feel free to
reopen if you disagree.

You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20150504/6da9e8fa/attachment.html>

More information about the llvm-bugs mailing list