similar to: [LLVMdev] -fblocks?

We inject a typedef for size_t here: http://llvm.org/viewvc/llvm-project/cfe/trunk/lib/Sema/Sema.cpp?revision=218230&view=markup#l206 The typedef type is determined by calling getSizeType(). SizeType is (relevantly) calculated in two places: X86_64 http://llvm.org/viewvc/llvm-project/cfe/trunk/lib/Basic/Targets.cpp?revision=218666&view=markup#l3512 X86_32

I believe that we provide a definition of size_t inside the compiler itself when clang is in MSVC compatibility mode. On Tue, Sep 30, 2014 at 5:51 PM, Eric Mader <emader at gmx.us> wrote: > I did some more investigation of the size_t size error. I misunderstood > what was happening. It turns out that size_t is already defined before my > prefix header is included. I added the

I have some C++ source files that mix in small bits of Obj-C. On the Mac, these files are marked to be compiled as Obj-C++. Looking at the clang help, it seems that the option for that is "-ObjC++". However, when I add that in Additional Options I get an error message: CL> : error : invalid integral value 'bjC++' in '-ObjC++' I see this same message if I put

Your install dir has a whitespace. Have you tried quoting? e.g. <LLVMInstallDir>"C:\Program Files (x86)\LLVM"</LLVMInstallDir> Best regards, Rafael Auler On Mon, Sep 29, 2014 at 7:38 PM, Eric Mader <emader at gmx.us> wrote: > I changed tooset-vs2013.props to this: > > <Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003" >

I replaced all instances of "$(Platform)" with "x64" for the x64 .props file and it still fails, so it looks like that guess was wrong as well. Regards, Eric On 9/29/14, 2:11 PM, Eric Mader wrote: > Quoting doesn't seem to make a difference. Strangely, the Win32 > toolset seems to work. (Where "work" means that clang runs and > produces a bunch of

Open the file toolset-vs2013.props and you'll understand what's happening and where the path is set. It tries to fetch the LLVM installation path from the Windows registry. Just fix this (maybe editing your registry or editing the .props file, whatever suits you best). On Mon, Sep 29, 2014 at 5:33 PM, Eric Mader <emader at gmx.us> wrote: > I copied the x64 toolsets by hand and

Hi Reid, I copied the x64 toolsets by hand; they got installed to C:\Program Files (x86)\LLVM\tools\msbuild\x64; they just didn't get moved correctly by install.bat. I just verified that the LLVM-vs2013 toolset.props is correct. If it is a bitness problem, perhaps I'm failing to define something correctly? Regards, Eric On 9/30/14, 11:29 AM, Reid Kleckner wrote: > This looks

I'm getting compile errors because size_t is getting redefined. My "forced include file" starts with: #if BUILDING_FOR_WINDOWS #define NOMINMAX /* deal with the fact that windef.h also defines BOOL */ #define BOOL WINBOOL #include <windows.h> #include <intrin.h> #undef BOOL #endif Looking at the preprocessor expansion of a typical .cpp file, I see that crtdefs.h

I was hoping to not have to build LLVM myself, especially on Windows. Can anybody help me with the Windows installer? Failing that, I find the directions for how to compile on Windows hard to follow? Can I build using Cygwin? Regards, Eric On 9/29/14, 8:11 AM, Rafael Auler wrote: > I'm not sure about the Windows installer, but if you build and install > LLVM for Windows from the

I'm trying to port a bunch of code from MacOS X to Windows. The code is a mixture of C, C++11 and Objective-C. (Some of the C++ code has bits of Objective-C mixed in, just for spice ;-) Since it builds on the Mac with clang, I thought that building on Windows with clang would mean that I wouldn't have to make a bunch of changes just related to a different compiler. For example, if I

Hi Hans, Answers inline below. Regards, Eric On 9/30/14, 8:05 AM, Hans Wennborg wrote: > On Mon, Sep 29, 2014 at 7:56 PM, Eric Mader <emader at gmx.us> wrote: >> Hi Hans, >> >> I think installer.bat found my visual Studio installation because it >> installed the Win32 toolsets but not the x64 ones. (It took me a while to >> work this out ;-) I installed

I’m trying to install LLVM-3.6.0-r218288-win32.exe on Windows 7 Ultimate x64. The install doesn’t complain, but the toolset doesn’t show up in either Visual Studio 2013 or Visual Studio 2010. Also I selected the choices to add LLVM to the path for every user and put an LLVM icon on the desktop. Neither of this happened. Can anyone tell me how to get this to work? Regards, Eric Mader

Hi Reid, Thanks for the reply. Comments inline below. Regards, Eric On 9/29/14, 5:51 PM, Reid Kleckner wrote: > I think any port will involve some changes, but it's really hard to > say which porting approach will be the least painless beforehand. > Aside from _MSC_VER incompatibilities messing up portability headers, > I think any changes you make to support clang on Windows

Hi Hans, I think installer.bat found my visual Studio installation because it installed the Win32 toolsets but not the x64 ones. (It took me a while to work this out ;-) I installed the x64 toolsets by hand and they seem to work. I think the installer ran as administrator. I explicitly ran it that way again (asking it to uninstall first) just to be sure. It didn't seem to make any

Hello, i try to compile a small test programm with clang and the command line option -fblocks. clang -m32 -march=i686 -D__COCOTRON__ -DWINDOWS -D_GNU_SOURCE -D__LITTLE_ENDIAN__ -D_FORTIFY_SOURCE=1 -x objective-c -fobjc-exceptions -fconstant-string-class=NSConstantString -O2 -Wno-unknown-pragmas -fmessage-length=0 --std=c99 -pipe -Ic:/devel/tools/mingw64/lib/gcc/x86_64-w64-mingw32/4.7.1/include

I'm using Samba 2.0.6 on a Linux server. When using smbmount or mount to mount a share from an NT server, how do I set file permissions. An older smbmount allowed a -d and -f switch to set the file permissions. The newest one does not support these. The man pages for smbmount and smbmnt mention using syntax that does not work. I finally have gotten the mount command to work, but now I

Jack, this is not a problem of this patch, this a problem of your configuration. This patch uses standard clang machinery for locating libiomp5 library. Best regards, Alexey Bataev ============= Software Engineer Intel Compiler Team 13.05.2015 15:59, Jack Howarth пишет: > On Tue, May 12, 2015 at 3:58 PM, <andreybokhanko at gmail.com> wrote: >> Jack, >> >> Alexey

Hi all, I am running SuSE 6.2 on a machine with 2 processors, so I just recompiled the kernel to pick up the second cpu. I now have problems using smbmount (2.0.5a that came with distrubution) or using the newer mount syntax (I just installed 2.0.6) to mount a share from an NT 4.0 server. After issuing the smbmount/mount command, and then going to the mount point, I get i/o errors on the

I'm trying to add a new option to clang to enable my auto profile pass. I've added this to Options.td and Driver/Tools.cpp, but I'm not getting the option -auto-profile in cc1's invocation. I've checked that the code to push -auto-profile is executed, but if use -v, I don't see -auto-profile in the cc1 invocation. Can anyone point me to some document that explains how to

I'm having a strange problem compiling with VS 2013. It's not finding a header file that's there in one of the header file search dirs. Here's the compile command (with the names changed to protect the innocent ;-) 1> C:\Program Files (x86)\LLVM\msbuild-bin\CL.exe /c /IC:\[top-level-dir]\[source-dir]\ /IC:\[top-level-dir]\[source-dir]\[sub-dir-1]