search for: vs2019

...beginning of December. The Polly test fails since a few days ago. (see below for more info) I'm using the following cmake cmd-line: cmake -GNinja %ROOT%/llvm -DCMAKE_BUILD_TYPE=Release -DLLVM_OPTIMIZED_TABLEGEN=ON -DLLVM_ENABLE_ASSERTIONS=ON -DLLVM_ENABLE_LIBXML2=OFF -DCMAKE_C_COMPILER="%VS2019%/bin/HostX64/x64/cl.EXE" -DCMAKE_CXX_COMPILER="%VS2019%/bin/HostX64/x64/cl.EXE" -DCMAKE_LINKER="%VS2019%/bin/HostX64/x64/link.EXE" -DLLVM_ENABLE_PROJECTS="llvm;clang;lld;clang-tools-extra;compiler-rt;mlir;polly" -DLLVM_ENABLE_PDB=ON -DLLVM_POLLY_LINK_INTO_TOOLS=ON...

AFAICT we traditionally only support building llvm/clang with the 2 most recent releases of Visual Studio. With the release of VS2019, what do people think of retiring VS2015 support before the next major llvm/clang release? As well as simplifying C++14 migration (admittedly only a little), this should also let us remove a number of hacks (e.g. the alignas/AlignedCharArray hack in AlignOf.h), as well as re-enabling a number...

Hi. Just now when I tried to compile a .cpp file using the LLVM toolset in VS2019, I got two error messages from lld-link: " lld-link : error : Debug\cust_std_lib_facilities.obj: unknown file type lld-link : error : Debug\Ex10_10.obj: unknown file type " What's the reason for this, and is there a way to fix it? This is the first time I'm saying this error; I...

...gt;> >> >> >> I’m using the following cmake cmd-line: >> >> >> >> cmake -GNinja %ROOT%/llvm -DCMAKE_BUILD_TYPE=Release >> -DLLVM_OPTIMIZED_TABLEGEN=ON -DLLVM_ENABLE_ASSERTIONS=ON >> -DLLVM_ENABLE_LIBXML2=OFF >> -DCMAKE_C_COMPILER="%VS2019%/bin/HostX64/x64/cl.EXE" >> -DCMAKE_CXX_COMPILER="%VS2019%/bin/HostX64/x64/cl.EXE" >> -DCMAKE_LINKER="%VS2019%/bin/HostX64/x64/link.EXE" >> -DLLVM_ENABLE_PROJECTS="llvm;clang;lld;clang-tools-extra;compiler-rt;mlir;polly" >> -DLLVM_ENABLE_PD...

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/attachm...

...list of failing tests - generic Visual Studio Docker image <https://github.com/llvm/llvm-zorg/tree/master/buildbot/google/docker/windows-base-vscode2019> and the 32bit buildbot Docker image <https://github.com/llvm/llvm-zorg/tree/master/buildbot/google/docker/buildbot-windows10-vs2019> - Deployment <https://github.com/llvm/llvm-zorg/blob/master/buildbot/google/terraform/main.tf> of the container on Google Cloud. - Additional documentation <https://github.com/llvm/llvm-zorg/tree/master/buildbot/google> on the setup Best, Christian -------------...

...wards-binary-compatibility with the VS 2015 series compilers, so the initial VS2017 compiler was version 19.10. We continued the practice of bumping the second decimal place for each toolset update, which is a less frequent occurrence than a VS update, so the VS 2017 15.9 compiler is version 19.16. VS2019 will similarly start at 19.20. So yes, "19.1 or higher" is "any old VS2017 version." On Fri, Feb 8, 2019 at 10:22 AM via cfe-dev <cfe-dev at lists.llvm.org> wrote: > Note that the minimum version of "Visual Studio 2017" is not "any old > Visual Stud...

Hi. I'm trying to build LLVM 10.0.0 with CMake on the command line (Developer Command Prompt for VS2019) and I need to know how to switch to a static runtime. I've tried setting LLVM's variable for this, but it didn't work. I still have a dynamic runtime. Along with that, I also need to know how to enable C++ exceptions. One thing I tried was to do "-DCMAKE_CXX_FLAGS="/std:c...

Hello compiler fans! As discussed in the RFC <http://lists.llvm.org/pipermail/llvm-dev/2019-January/129452.html>, LLVM’s cmake configuration now soft-errors if you use an older toolchain to build. The new minimums are: * Clang 3.5 * Apple Clang 6.0 * GCC 5.1 * Visual Studio 2017 You can opt-out of the soft-error with LLVM_TEMPORARILY_ALLOW_OLD_TOOLCHAIN. You’ll still want to update your

Hey list, TL;DR - LLVM 10 is around 7-8% slower than LLVM 9 when compiling the same inputs. So here at Unity our Burst HPC# compiler uses LLVM to provide our users with some very optimal codegen. LLVM is used in two ways: 1. In the Unity editor we JIT compile user code. 2. We also have an AOT mode for when our users are building a full game. Particularly for 1., compile time really matters for