Osman Zakir via llvm-dev
2019-Oct-31 13:43 UTC
[llvm-dev] Recent LLVM Build Attempt -- obj.ClangAST.vcxproj Failed to Build
I hope I'm not being too presumptuous or anything when I say this: could you guys please review the obj.ClangAST.vcxproj project and try to fix the ambiguity error? Reid asked me why I'm using C++17. I just want to use the latest released standard. Most if it still compiles anyway. So I'll stick with it. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20191031/c2234826/attachment.html>
Jonathan Meier via llvm-dev
2019-Oct-31 18:11 UTC
[llvm-dev] Recent LLVM Build Attempt -- obj.ClangAST.vcxproj Failed to Build
From a quick glance at the build log, you should be able to avoid the ambiguity by removing the alias template `template <typename T> using Optional = llvm::Optional<T>;` from the files ByteCodeExprGen.cpp and ByteCodeStmtGen.cpp in clang/lib/AST/Interp. Note that this is just my best guess, I didn‘t try it myself. I‘m also not sure why MSVC sees an ambiguity here. Am 31.10.2019 um 14:44 schrieb Osman Zakir via llvm-dev <llvm-dev at lists.llvm.org>: I hope I'm not being too presumptuous or anything when I say this: could you guys please review the obj.ClangAST.vcxproj project and try to fix the ambiguity error? Reid asked me why I'm using C++17. I just want to use the latest released standard. Most if it still compiles anyway. So I'll stick with it. _______________________________________________ LLVM Developers mailing list llvm-dev at lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20191031/fdd39227/attachment.html>
Reid Kleckner via llvm-dev
2019-Oct-31 21:31 UTC
[llvm-dev] Recent LLVM Build Attempt -- obj.ClangAST.vcxproj Failed to Build
I went ahead and did that in 19f1dc7. I wasn't able to reproduce the problem locally, but I am not building through Visual Studio, I am using ninja. To build in C++17 mode, I just re-ran with -std:c++17, and got warnings but no errors. On Thu, Oct 31, 2019 at 11:11 AM Jonathan Meier <jonathan.meier at outlook.com> wrote:> From a quick glance at the build log, you should be able to avoid the > ambiguity by removing the alias template > > `template <typename T> using Optional = llvm::Optional<T>;` > > from the files ByteCodeExprGen.cpp and ByteCodeStmtGen.cpp in > clang/lib/AST/Interp. > > Note that this is just my best guess, I didn‘t try it myself. I‘m also not > sure why MSVC sees an ambiguity here. > > > Am 31.10.2019 um 14:44 schrieb Osman Zakir via llvm-dev < > llvm-dev at lists.llvm.org>: > > > I hope I'm not being too presumptuous or anything when I say this: could > you guys please review the obj.ClangAST.vcxproj project and try to fix the > ambiguity error? > > Reid asked me why I'm using C++17. I just want to use the latest released > standard. Most if it still compiles anyway. So I'll stick with it. > > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20191031/5ead1aae/attachment.html>