similar to: [LLVMdev] MSVC cstdint

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

I have a warning when building with MSVC2k5, a benign warning, but I am trying to get rid of them. ..\..\..\..\trunk\lib\Transforms\Utils\AddrModeMatcher.cpp(208) : warning C4334: '<<' : result of 32-bit shift implicitly converted to 64 bits (was 64-bit shift intended?) The line of code is: Scale = 1 << Scale; Where Scale is an int64_t, however, 1 is an int32_t (since

I have a warning when building with MSVC2k5, a benign warning, but I am trying to get rid of them. ..\..\..\..\trunk\lib\Transforms\Utils\AddrModeMatcher.cpp(208) : warning C4334: '<<' : result of 32-bit shift implicitly converted to 64 bits (was 64-bit shift intended?) The line of code is: Scale = 1 << Scale; Where Scale is an int64_t, however, 1 is an int32_t (since

Does not seem to be a straight error with LLVM itself, but rather the tools, linking issues, here are the errors: Opt: 30> Creating library R:\SDKs\llvm\trunk_VC8_building\lib\Debug\opt.lib and object R:\SDKs\llvm\trunk_VC8_building\lib\Debug\opt.exp 30>LLVMScalarOpts.lib(IndVarSimplify.obj) : error LNK2019: unresolved external symbol "public: bool __thiscall

Hi all, I''ve just noticed that 0.10 is out and wanted to give it a try on windows. I''m not at all an VS C++ Developer so I might do something very stupid here. My env: Windows Server 2003 VS .NET 2003 On the command line with nmake from VC7 in the path this is what I get: Attempting remote update of ferret Building native extensions. This could take a while... Microsoft

On Tue, May 12, 2009 at 11:55 PM, Chris Lattner <clattner at apple.com> wrote: > Dan, can you add IVUsers.cpp to the appropriate cmakefile? > > -chris > > > On May 12, 2009, at 10:54 PM, OvermindDL1 wrote: > >> On Tue, May 12, 2009 at 11:40 PM, Chris Lattner <clattner at apple.com> >> wrote: >>> >>> On May 12, 2009, at 10:24 PM,

Hi! when compiling projects using llvm 2.9 and ms vc 10 I get these warnings: 1>e:\Jochen\Lib\lib\include\llvm/Use.h(218): warning C4624: 'llvm::AugmentedUse' : destructor could not be generated because a base class destructor is inaccessible 1>C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\stdint.h(72): warning C4005: 'INT8_MIN' : macro redefinition

Hi! In DataTypes.h (generated from DataTypes.cmake) there is an extra code path for Visual C. This can produce macro redefinitions for INT8_MAX, INT8_MIN etc. since other headers may also define them. Therefore please protect the macros like INT8_C etc. Also it would be nice if the auto-generated HAVE_STDINT_H and HAVE_INTTYPES_H would be used also for Visual C since it is possible to add them

Hello, I've encountered two serious issues that have stopped me in my tracks, and I would be most grateful to anyone who can provide some answers. I am using the examples provided on the page "Testing the Embeddable R Library". I am writing a C application, that I want to embedd R into (I'm not interested in embedding my application in R, that's not an option). I'm

[please CC the llvm mailing list] Jochen Wilhelmy <j.wilhelmy at arcor.de> writes: >> What's that extra code path? >> > > #ifndef _MSC_VER > ... > #else /* _MSC_VER */ > /* Visual C++ doesn't provide standard integer headers, but it does provide > built-in data types. */ > > ... extra code path ... > > #endif Sorry, that doesn't

On Fri, Jan 29, 2016 at 6:27 PM, Matthias Braun via llvm-commits < llvm-commits at lists.llvm.org> wrote: > The point I was trying to make here is that all things that DataTypes.h > provides: > intXXX_t, uintXX_t, PRIdXX, INT64_MAX, HUGE_VAL, ssize_t ... > are all part of the C++11 standard and can be found in <cstdint>, <cmath> > (except for ssize_t) so I

Oh I did not know about DataTypes.h. However given that there are already two other files in llvm (in the AMDGPU and Hexagon targets) that #include <cstdint> since 2014, maybe we can loosen the requirement for DataTypes.h nowadays as #include <cstdint> seems to be working everywhere? - Matthias > On Jan 29, 2016, at 3:06 PM, Craig Topper <craig.topper at gmail.com> wrote:

Dear R users, I have a dataframe (main.table) with ~30,000 rows and 6 columns, of which here are a few rows: id chr window gene xp.norm xp.top 129 1_32 1 32 TAS1R1 1.28882115 FALSE 130 1_32 1 32 ZBTB48 1.28882115 FALSE 131 1_32 1 32 KLHL21 1.28882115 FALSE 132 1_32 1 32 PHF13 1.28882115 FALSE 133 1_33 1

DataTypes.h is transitively included through a lot of very common includes already. So its entirely possible AMDGPU and Hexagon are really including it. On Fri, Jan 29, 2016 at 5:02 PM, mats petersson <mats at planetcatfish.com> wrote: > Sounds to me like including `DataTypes.h` would be the right choice, since > it will include `stdint.h` if it exists - and error if it doesn't,

The question is addressed to Linux RPM-packagers. Hello! I was trying to rebuild rc17 binaries from dovecot-1.0-1_38.rc17.at.src.rpm taken at ATrpms <http://ATrpms.net/>. The process fails with following messages: -------------------- Making install in imap-quota make[3]: Entering directory `/usr/src/asplinux/BUILD/dovecot-1.0.rc15/src/plugins/imap-quota' make[4]: Entering

This one includes the latest App.cpp which includes the Mac fix from Nick. I thought it was in 0.0.11, but it wasn''t. It also adds support for "stock objects", like colours, pens, and fonts. This turned out to be quite challenging, but I''m happy with the solution. It only took a few days :-/ Kevin

I just pushed a new wxruby-swig, which includes the known MSWin rakefile changes. It also has some significant internal improvements that will make it easier to add classes, and it includes support for one new class (wxEvent). wxruby-swig is now licensed under the "MIT license". wxRuby will remain under the wxWindows license as long as we are releasing the old code base. When we

Joerg Sonnenberger via llvm-dev <llvm-dev at lists.llvm.org> writes: > On Mon, Jun 20, 2016 at 05:05:18PM +0000, Paweł Bylica via llvm-dev wrote: >> On Sun, Jun 19, 2016, 17:57 Joerg Sonnenberger <joerg at bec.de> wrote: >> >> > On Sun, Jun 19, 2016 at 03:24:22PM +0000, Paweł Bylica via llvm-dev wrote: >> > > Hi LLVM, >> > > >>