search for: wd4355

...se anyone knows what (or how to find out what) the actual command to compile Kaleidoscope is? I followed cmake/nmake down through maybe half a dozen levels before getting lost, so I tried to develop a compiler invocation from scratch. I got as far as cl /EHsc /I\d\llvm-2.6\include /I\llvm\include /wd4355 toy.cpp which successfully generated toy.obj and spat out 86 link time error messages -- as expected, it needs the libraries specified. cmakelists.txt says set(LLVM_LINK_COMPONENTS core jit interpreter native) so I made a guess at the .lib file corresponding to the first of these, and tried cl /E...

...how to find out what) the actual > command to compile Kaleidoscope is? I followed cmake/nmake down > through maybe half a dozen levels before getting lost, so I tried to > develop a compiler invocation from scratch. I got as far as > > cl /EHsc /I\d\llvm-2.6\include /I\llvm\include /wd4355 toy.cpp > > which successfully generated toy.obj and spat out 86 link time error > messages -- as expected, it needs the libraries specified. > cmakelists.txt says set(LLVM_LINK_COMPONENTS core jit interpreter > native) so I made a guess at the .lib file corresponding to the first &g...

...is my build command on windows. cl /EHsc -ID:\LLVM\llvm-3.4.2\build_nmake\output/include -D_CRT_SECURE_NO_DEPRECATE -D_CRT_SECURE_NO_WARNINGS -D_CRT_NONSTDC_NO_DEPRECATE -D_CRT_NONSTDC_NO_WARNINGS -D_SCL_SECURE_NO_DEPRECATE -D_SCL_SECURE_NO_WARNINGS -wd4146 -wd4180 -wd4244 -wd4267 -wd4345 -wd4351 -wd4355 -wd4503 -wd4624 -wd4800 -wd4291 -w14062 -we4238 -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -c testpass.cpp cl /D_USRDLL /D_WINDLL testpass.obj /link /DLL /OUT:testpass.dll D:\LLVM\llvm-3.4.2\build_nmake\output\lib\LLVMCore.lib ... (including other LLVM libraries) Thanks...

Thanks to OvermindDL1 for pointing this out: compiling with Visual C++ actually works! Basically it's just a matter of running cmake (default settings are fine) then nmake, and I've got what appears to be a working version of LLVM. Kaleidoscope crashes on attempting to exit with ^Z: C:\llvm\bin>Kaleidoscope.exe ready> 1+2; ready> Evaluated to 3.000000 ready> 3*4; ready>

I'm trying to get the Kaleidoscope tutorial mini compiler working on Windows (as a trial run for developing a compiler using LLVM). Kaleidoscope uses the C++ linkage method of code generation (as opposed to spitting out intermediate code in a text or binary file), which as I understand it is the preferred way of doing it for a few reasons, one of them being that it gives you JIT capability,

...t) the actual >> command to compile Kaleidoscope is? I followed cmake/nmake down >> through maybe half a dozen levels before getting lost, so I tried to >> develop a compiler invocation from scratch. I got as far as >> >> cl /EHsc /I\d\llvm-2.6\include /I\llvm\include /wd4355 toy.cpp >> >> which successfully generated toy.obj and spat out 86 link time error >> messages -- as expected, it needs the libraries specified. >> cmakelists.txt says set(LLVM_LINK_COMPONENTS core jit interpreter >> native) so I made a guess at the .lib file correspon...

...at is where the failure is I'm building LLVM. The failure in the buildbot happens when compiling HexagonFrameLowering.cpp: ---------- FAILED: C:\PROGRA~2\MICROS~1.0\VC\bin\cl.exe /nologo /TP /DWIN32 /D_WINDOWS /W4 -wd4141 -wd4146 -wd4180 -wd4244 -wd4258 -wd4267 -wd4291 -wd4345 -wd4351 -wd4355 -wd4456 -wd4457 -wd4458 -wd4459 -wd4503 -wd4624 -wd4722 -wd4800 -wd4100 -wd4127 -wd4512 -wd4505 -wd4610 -wd4510 -wd4702 -wd4245 -wd4706 -wd4310 -wd4701 -wd4703 -wd4389 -wd4611 -wd4805 -wd4204 -wd4577 -wd4091 -wd4592 -wd4319 -wd4324 -w14062 -we4238 /Zc:inline /Oi /Zc:rvalueCast /MD /O2 /Ob2 /D N...

...ws, this using MSVC 2013. I am basically getting things like: --------------------------------------- FAILED: C:\PROGRA~2\MICROS~2.0\VC\bin\X86_AM~1\cl.exe /nologo /TP /DWIN32 /D_WINDOWS /GR /EHsc /DNDEBUG /MD /O2 /Ob2 /wd4267 /wd4146 /wd4180 /wd4244 /wd4258 /wd4267 /wd4291 /wd4345 /wd4351 /wd4355 /wd4456 /wd4457 /wd4458 /wd4459 /wd4503 /wd4624 /wd4722 /wd4800 /w14062 /we4238 -Isrc\plugins\thirdParty\LLVM -I..\src\plugins\thirdParty\LLVM -I..\src\misc -I..\src\plugins -I..\src\plugins\miscellaneous\Core\src -I..\src\3rdparty\QtSingleApplication\src -I..\src\plugins\thirdParty\LLVM\include -I...

...gt; using 'struct' [snipped some more warnings] > The rest of the project compiles clean in non-pedantic mode, quite > wonderful. :) Not so wonderful. Lots of warnings are disabled: add_llvm_definitions( -wd4146 -wd4503 -wd4996 -wd4800 -wd4244 -wd4624 ) add_llvm_definitions( -wd4355 -wd4715 -wd4180 -wd4345 -wd4224 ) add_llvm_definitions( -wd4351 ) It's very likely that some of those warnings are really useful (i.e. are hinting at bugs.) OTOH, keeping LLVM warning-free for VC++ and gcc at the same time looks like a never-ending uphill battle. -- Óscar

In DataTypes.h starting on line 121 are these lines: #define INT8_C(C) C #define UINT8_C(C) C #define INT16_C(C) C #define UINT16_C(C) C #define INT32_C(C) C #define UINT32_C(C) C ## U #define INT64_C(C) ((int64_t) C ## LL) #define UINT64_C(C) ((uint64_t) C ## ULL) They are conflicting with the cstdint when we have updated headers in our MSVC build. I could have sworn I talked about this

On Mon, Nov 24, 2008 at 8:18 PM, Óscar Fuentes <ofv at wanadoo.es> wrote: > OvermindDL1 <overminddl1 at gmail.com> writes: > >>> Chris proposed on IRC to remove the Visual Studio project files and turn >>> CMake into the "standard" for building LLVM with VC++. >>> >>> If you have strong arguments against this, please voice them.

.../EHsc -ID:\LLVM\llvm-3.4.2\build_nmake\output/include >> -D_CRT_SECURE_NO_DEPRECATE -D_CRT_SECURE_NO_WARNINGS >> -D_CRT_NONSTDC_NO_DEPRECATE -D_CRT_NONSTDC_NO_WARNINGS >> -D_SCL_SECURE_NO_DEPRECATE -D_SCL_SECURE_NO_WARNINGS -wd4146 -wd4180 >> -wd4244 -wd4267 -wd4345 -wd4351 -wd4355 -wd4503 -wd4624 -wd4800 -wd4291 >> -w14062 -we4238 -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS >> -D__STDC_LIMIT_MACROS -c testpass.cpp >> >> cl /D_USRDLL /D_WINDLL testpass.obj /link /DLL /OUT:testpass.dll >> D:\LLVM\llvm-3.4.2\build_nmake\output\lib\LLVMCore.lib...

...ws, this using MSVC 2013. I am basically getting things like: --------------------------------------- FAILED: C:\PROGRA~2\MICROS~2.0\VC\bin\X86_AM~1\cl.exe /nologo /TP /DWIN32 /D_WINDOWS /GR /EHsc /DNDEBUG /MD /O2 /Ob2 /wd4267 /wd4146 /wd4180 /wd4244 /wd4258 /wd4267 /wd4291 /wd4345 /wd4351 /wd4355 /wd4456 /wd4457 /wd4458 /wd4459 /wd4503 /wd4624 /wd4722 /wd4800 /w14062 /we4238 -Isrc\plugins\thirdParty\LLVM -I..\src\plugins\thirdParty\LLVM -I..\src\misc -I..\src\plugins -I..\src\plugins\miscellaneous\Core\src -I..\src\3rdparty\QtSingleApplication\src -I..\src\plugins\thirdParty\LLVM\include -I...

OvermindDL1 <overminddl1 at gmail.com> writes: >> Chris proposed on IRC to remove the Visual Studio project files and turn >> CMake into the "standard" for building LLVM with VC++. >> >> If you have strong arguments against this, please voice them. > > As long as instructions are supplied on how to pass in user defined > macros to the build system.

...lt: if( MSVC ) add_definitions( -D_CRT_SECURE_NO_DEPRECATE -D_CRT_SECURE_NO_WARNINGS ) add_definitions( -D_SCL_SECURE_NO_WARNINGS -DCRT_NONSTDC_NO_WARNINGS ) add_definitions( -D_SCL_SECURE_NO_DEPRECATE ) add_definitions( -wd4146 -wd4503 -wd4996 -wd4800 -wd4244 -wd4624 ) add_definitions( -wd4355 -wd4715 ) endif( MSVC ) > In addition to those, for Release builds I recommend disabling the > "secure" stdlib features which does bounds checking and slows down a > lot of good code: > > _SECURE_SCL=0 // slow secure stdlib. This isn't, but adding an option for just o...

It works for me: ------ Build started: Project: LLVMHexagonCodeGen, Configuration: RelWithDebInfo Win32 ------ cl : Command line warning D9002: ignoring unknown option '/Zc:inline' HexagonFrameLowering.cpp ========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ========== Here's the info from the "about" window: Microsoft Visual Studio Professional 2013

>There's a config.h file in the win32 subdirectory that implies that it's >supposed to be concatenated as part of the build process, but it doesn't >seem like that's happening from within the .sln script--am I missing a >pre-build step someplace? When config.h.in is hit in the build of configure the configure project, the configure.h file from the win32 directory is