search for: wd4715

Displaying 5 results from an estimated 5 matches for "wd4715".

Did you mean: 24715
2009 Dec 08
0
[LLVMdev] VC++ warnings (was: Macro redefinitions)
...g '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
2009 Dec 07
2
[LLVMdev] Macro redefinitions
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
2008 Nov 25
0
[LLVMdev] Removal of Visual Studio project files.
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.
2008 Nov 25
2
[LLVMdev] Removal of Visual Studio project files.
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.
2008 Nov 25
2
[LLVMdev] Removal of Visual Studio project files.
...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 one defin...