Osman Zakir via llvm-dev
2019-Oct-10 14:47 UTC
[llvm-dev] Building For x64 Windows using LLVM
I'm trying to do it by passing "-Xclang -m64" on the VS2019 command line options panel but it gives the error "unknown argument" on "-m64". How do I do it? Thanks in advance. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20191010/37832cc8/attachment.html>
Reid Kleckner via llvm-dev
2019-Oct-10 17:32 UTC
[llvm-dev] Building For x64 Windows using LLVM
It should work if you remove -Xclang. clang-cl will recognize -m64. The clang -cc1 interface that clang-cl delegates to doesn't recognize -m64. It's implemented purely in the driver above the -cc1 invocation. On Thu, Oct 10, 2019 at 7:48 AM Osman Zakir via llvm-dev < llvm-dev at lists.llvm.org> wrote:> I'm trying to do it by passing "-Xclang -m64" on the VS2019 command line > options panel but it gives the error "unknown argument" on "-m64". How do > I do it? Thanks in advance. > _______________________________________________ > 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/20191010/48050670/attachment.html>
Reid Kleckner via llvm-dev
2019-Oct-10 20:36 UTC
[llvm-dev] Building For x64 Windows using LLVM
clang-cl recognizes -mllvm, so it shouldn't need escaping. And in general, if you find that clang-cl does not recognize a flag, I recommend prefixing it with -clang:, which causes clang to treat it as a GCC-style option in the driver instead of escaping it. The short version is, use /clang:-fblah instead of -Xclang -fblah if possible. On Thu, Oct 10, 2019 at 1:34 PM Osman Zakir <osmanzakir90 at hotmail.com> wrote:> Thanks for the reply. Is "-Xclang -mllvm" fine, or should I remove the > "-Xclang" from here as well? > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20191010/922f0c8d/attachment-0001.html>
Osman Zakir via llvm-dev
2019-Oct-10 22:16 UTC
[llvm-dev] Building For x64 Windows using LLVM
Okay, so I can use -std:c++17 with clang-cl.exe? I guess it was adopted from /std:c++17 which the regular cl.exe uses. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20191010/abf9b965/attachment.html>
Zachary Turner via llvm-dev
2019-Oct-11 01:46 UTC
[llvm-dev] Building For x64 Windows using LLVM
You can typically copy and paste a cl command line and it will work, and clang-cl accepts dashes or slashes, so yes On Thu, Oct 10, 2019 at 3:16 PM Osman Zakir via llvm-dev < llvm-dev at lists.llvm.org> wrote:> Okay, so I can use -std:c++17 with clang-cl.exe? I guess it was adopted > from /std:c++17 which the regular cl.exe uses. > > _______________________________________________ > 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/20191010/f3443746/attachment.html>
Apparently Analagous Threads
- lld-link.exe Can't Recognize .obj File Type?
- How to Switch to Static Runtime and Enable C++ Exceptions?
- Have LLD and Clang in their correct locations, but still can't generate project files for LLVM
- Have LLD and Clang in their correct locations, but still can't generate project files for LLVM
- Have LLD and Clang in their correct locations, but still can't generate project files for LLVM