search for: vs2017

...Osman Zakir via llvm-dev <llvm-dev at lists.llvm.org> Reply-To: Osman Zakir <osmanzakir90 at hotmail.com> Date: Thursday, December 7, 2017 at 7:09 AM To: "llvm-dev at lists.llvm.org" <llvm-dev at lists.llvm.org> Subject: [llvm-dev] Updating LLVM/Clang support for VS for VS2017 The Clang compiler doesn't have full support for VS2017 yet, right? I talked to someone on MSDN forums and they said that LLVM/Clang developers still haven't updated Clang's VS support to include VS2017. The patch for finding VS2017 installation instances and toolchains was updated,...

my build environment: Win7 x64 VStudio 2017 Community Edition 15.8.4 (latest) CMake 3.12.1 (x86) git 2.19.0 (latest, x64) Python 2.7.2 (x86) my build steps: open VS2017 x64 developer command prompt cd D:\projects\fun\jit_tests mkdir llvm cd llvm git clone https://github.com/llvm-mirror/llvm mkdir llvm-build cd llvm-build cmake -G "Visual Studio 15 2017 Win64" -DBUILD_SHARED_LIBS=ON -DLLVM_TARGETS_TO_BUILD=host -DLLVM_ENABLE_WARNINGS=OFF -DLLVM_INCLUDE_...

...The compiler in the first VS 2015 release was version 19.00. For each update/hotfix release, we bumped that version by .01. When VS 2017 was released, we decided to keep the major compiler version the same to signify backwards-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 "...

i want to integrate a C source JITer into my application but the resulting executables are too large is it possible to reduce the resulting libs/exe some way? current VS2017/svn build example: llvm-build\Release\bin\clang-interpreter.exe ~36MB for now (that can change later) - i want to jit simple c-code - no std library or something - x64 only - no deep/full architecture optimization needed - no c++/templates etc. any ideas?

Thank you very much,It works! And some Q&A I meet,may help somebody: 1. If zlib build with 32bit,should use MSVC's 'vcvars32.bat'; 2. Add '-Z7' to CXXFLAGS can release *.pdb file for VS2017 'Step Into' debug, such as: CXXFLAGS="-EHsc -Z7"; 3. If Somebody write a demo in VS2017 3.1 change libxapian.a's name to libxapian.lib; 3.2 make sure the Runtime Library is /MT, can change it at project property page, C/C++-->Code Generation-->Runtime Library; 3.3 a...

...only xapian-core. As I wrote on my case compilation with Visual Studio 2015 successful, just I have runtime errors, while the same code on LINUX runs fine. I'll try the hints from (https://trac.xapian.org/browser/git/xapian-core/INSTALL?rev=RELEASE/1.4#L54) and maybe to migrate my project to VS2017 and test it again. If I understand correctly starting from 1.4.6 you will have officiant MSVC support? What is a approximate date for this release? Thank you again. Sincerely, Davit On 30.04.2018 03:16, Olly Betts wrote: > On Sun, Apr 29, 2018 at 06:31:33PM +0200, Kalantaryan, Davit wrote: &g...

...and line (to tell it > > to use the Microsoft linker). > And some Q&A I meet,may help somebody: Thanks for these - I'll update INSTALL. > 1. If zlib build with 32bit,should use MSVC's 'vcvars32.bat'; > 2. Add '-Z7' to CXXFLAGS can release *.pdb file for VS2017 'Step Into' debug, such as: CXXFLAGS="-EHsc -Z7"; > 3. If Somebody write a demo in VS2017 > 3.1 change libxapian.a's name to libxapian.lib; > 3.2 make sure the Runtime Library is /MT, can change it at project property page, C/C++-->Code Generation-->Runtime L...

By default, FLAC requires ogg library. Support of old versions of Visual Studio was removed from libogg code about 2 years ago: https://git.xiph.org/?p=ogg.git;a=commit;h=18c401c6bc8814d06f3ae53ebf5d4399f90871cc libogg 1.3.3 (released 2017-11-07) cannot be built with MSVS 2005/2008 anymore. Are there any developers that want to use libFLAC in their programs and still use Visual Studio 2005 or

...nrelated big one is build again it could be that faster systems do not suffer that much from this behavior but it still does not feel right enough RAM, no swapping, just my 2 core CPU is not fast enough result: Fibonacci was built without errors after building i reopened llvm-build\LLVM.sln in VS2017 ... loading 273 projects and tested what happend on selecting "build solution" - to check what else happened to build now serveral cpp getting compiled, libs/exes getting linked - i think that is related to the X86CommonTableGen rebuild another >30min waiting to "finish buildin...

...(default) means: async exceptions + C++ exceptions, but no unwinding /EHa means: async exceptions + C++ exceptions, with unwinding in both cases /EHs means: C++ exceptions only, with unwinding I'm using MSVC VS2017 15.9.16 and clang-cl from github at HEAD. In both cases I'm targeting x64. Using _set_se_translator [4] and /EHa does not help with clang-cl. Are there any plans to improve the async exceptions unwinding in the short term? Thanks! Alex. [1] warning C4530: C++ exception handler used, but un...

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

...m currently investigating making use of LLVM for PDB parsing for with a view to supporting partial PDBs as produced by /DEBUG:FASTLINK as the VS DIA SDK hasn't been updated to handle them. I know this is probably low on your priority list but since /DEBUG:FASTLINK is now the implied default for VS2017 I figure it's a good time to take a look at it. Unfortunately I'm finding very little information on the internal structure used by partial PDBs. It seems https://github.com/Microsoft/microsoft-pdb doesn't offer much either, unless I'm missing something... So, two questions: Are y...

Sorry about that, let me check the correct version for the intrin0.h include guard. //Marcus ________________________________ From: Ralph Giles <giles at thaumas.net> Sent: Thursday, June 11, 2020 19:31 To: Marcus Asteborg <xnorpx at outlook.com>; opus at xiph.org <opus at xiph.org> Subject: Re: [opus] Misc patches Speaking of needing more complete ci feedback, the intrin0.h

....soluz at gmx.net> Subject: RE: [llvm-dev] Building LLVM with VisualStudio 2017 Hey Gaier, Can you give a few more details on your scenario? We use build LLVM with VS 2017 and we can successfully compile programs with clang afterwards. At a high level, what we do is: 1) Call Cmake to generate VS2017 Solution 2) Build the solution 3) Now use clang to compile other programs Thanks, -Stella -----Original Message----- From: llvm-dev <llvm-dev-bounces at lists.llvm.org> On Behalf Of Gaier, Bjoern via llvm-dev Sent: Friday, October 26, 2018 2:52 AM To: Dennis Luehring <dl.soluz at gmx.ne...

Thanks for your reply. I had run vcvars64.bat,but still cann't find 'cl'. Finally I fix it, change msys2_shell.cmd: "if it is present: replace rem set MSYS2_PATH_TYPE=inherit with set MSYS2_PATH_TYPE=inherit". And other errors : # ./configure CC="cl -nologo" CXX="$PWD/compile cl -nologo" CXXFLAGS="-EHsc AR=lib -IC:\zlib-1.2.3-lib\include

...build steps: cd llvm_build cmake -Thost=x64 -G "Visual Studio 15 2017 Win64" -DLLVM_TARGETS_TO_BUILD=host -DLLVM_BUILD_EXAMPLES=1 -DCLANG_BUILD_EXAMPLES=1 -DLLVM_INCLUDE_TESTS=OFF -DLLVM_INCLUDE_DOCS=OFF ..\llvm cmake --build . --config Debug after building i open llvm-build\LLVM.sln in VS2017 ... loading 273 projects question1: if left click on the solution root and select "build solution" (to check if everyhing is built) two files DummyClangFuzzer.cpp and ClangFuzzer.cpp getting compiled - is that indendet? then i want to add some tests to the Fibonacci example and added IR...

This patch adds 2 new functions, FLAC__lpc_restore_signal_intrin_sse41() and FLAC__lpc_restore_signal_16_intrin_sse41(). The decoding speed of Subset-compatible 16-bit FLAC files is slightly increased on SSE4.1-compatible CPUs. -------------- next part -------------- A non-text attachment was scrubbed... Name: 04_add_new_intrin_func.patch Type: application/octet-stream Size: 9851 bytes Desc: not

I don't like the decision to remove the old VS project files, in my opinion it's better to keep them, marked "not updated anymore". I personnally use VS2013, and the reason I don't want to upgrade is the fact that VS2017 requires online registration to work. I'm pretty sure some users also have valid reasons to keep their old VS. On 2 May 2018 at 14:37, lvqcl <lvqcl.mail at gmail.com> wrote: > By default, FLAC requires ogg library. Support of old versions of > Visual Studio was removed from libogg...

Verified that intrin0.h was available in 1910, by building it locally on VS2017 version 15.0 MSVC++ 14.1 _MSC_VER == 1910 (Visual Studio 2017 version 15.0) https://en.wikipedia.org/wiki/Microsoft_Visual_C%2B%2B //Marcus ________________________________ From: Marcus Asteborg <xnorpx at outlook.com> Sent: Thursday, June 11, 2020 20:15 To: Ralph Giles <giles at thau...

How is the LLVM toolchain built for Windows? I'm working on VS integration. Like, in Xcode, the actual *.xctoolchain bundle is built using the regular cmake files, plus using the cmake build script in tools/xcode-toolchain, what is the windows equivalent? is it literally just the stuff in tools/msbuild, or is there more to it than that? -------------- next part -------------- An HTML