similar to: [LLVMdev] [PATCH] Windows implementation of enable_execute_stack

Hi, I am trying to build llvm along with clang and compiler-rt. when I run make, I am getting the following compilation error: ... COMPILE: clang_linux/full-x86_64/x86_64:/home/pranav/smack-project/llvm/src/projects/compiler-rt/lib/enable_execute_stack.c /home/pranav/smack-project/llvm/src/projects/compiler-rt/lib/enable_execute_stack.c:53:29:error: cast to 'unsigned char *' from

Hi, I am trying to build llvm along with clang and compiler-rt. When I run make, I am getting the following compilation error (I tried compiling llvm-3.2, which is what I need for my project, but also tried llvm-3.3 and the current llvm source from the git repository). ... COMPILE: clang_linux/full-x86_64/x86_64:

You can disable -Werror by adding the cmake flag -DLLVM_ENABLE_WERROR=OFF, which should let it just ignore that (that's also the default, so you must have turned it on somewhere) On Jul 31, 2013, at 13:09 , Pranav Garg <pranav.garg2107 at gmail.com> wrote: > Hi, > > I am trying to build llvm along with clang and compiler-rt. When I run make, I am getting the following

On Thu, Aug 1, 2013 at 5:32 PM, Pranav Garg <pranav.garg2107 at gmail.com>wrote: > Dear Alexey, > > Yes I am sure that the llvm, clang and compiler-rt are synced to the same > version. I downloaded them all from git > http://llvm.org/docs/GettingStarted.html#git-mirror > I think I need compiler-rt for my project but I'll verify it again to see > if I can proceed

Dear Alexey, Yes I am sure that the llvm, clang and compiler-rt are synced to the same version. I downloaded them all from git http://llvm.org/docs/GettingStarted.html#git-mirror I think I need compiler-rt for my project but I'll verify it again to see if I can proceed without it. You are correct that compiler-rt is compiled with the just built clang. The complete command that gives an error

Hi Pranav, On Thu, Aug 1, 2013 at 1:54 AM, Pranav Garg <pranav.garg2107 at gmail.com>wrote: > Hi, > > I see that ENABLE_WERROR is being set to off (the default value) in the > config.log in the llvm build. However on grepping for WERROR in the > compiler-rt folder I get the following output: > > pranav at pranav:~/smack-project/llvm-3.4/src/projects/compiler-rt$ grep

yes I think that is correct. I wrote a simple program to print if sizeof(uintptr_t) != sizeof(unsigned char *) and when I compile with gcc -m64 and execute it on a 64-bit host (that is different from the 32-bit laptop on which I originally compiled the program), it says the sizes are not equal. Thanks Pranav On Thu, Aug 1, 2013 at 9:29 AM, Alexey Samsonov <samsonov at google.com> wrote:

Hi, I see that ENABLE_WERROR is being set to off (the default value) in the config.log in the llvm build. However on grepping for WERROR in the compiler-rt folder I get the following output: pranav at pranav:~/smack-project/llvm-3.4/src/projects/compiler-rt$ grep -Rin WERROR * lib/asan/tests/CMakeLists.txt:38: -Werror lib/asan/asan_malloc_mac.cc:253:// This function is currently unused, and we

---------- Forwarded message ---------- From: Ruben Van Boxem <vanboxem.ruben at gmail.com> Date: 2012/1/7 Subject: Re: [llvm-commits] [PATCH][Compiler-rt] Windows implementation of mmap functionality in clear_cache_test and enable_execute_stack_test To: Anton Korobeynikov <anton at korobeynikov.info> 2012/1/7 Anton Korobeynikov <anton at korobeynikov.info> > Hello Ruben

Nick, I had a few minutes so I implemented the WxPrinterDC class tonight, and I have a question on Virtual Methods. Is there a general rule of thumb to follow? Should they be implemented in the wxRuby header and source files, or should I ignore them? They are not listed on the WxWidgets documentation page, but they are in the wxWidgets source file, as being public virtual methods. Examples:

Whoops, phone rang and I forgot to cc to the list before I typed the message. ----- Forwarded Message ---- > From: Samuel Crow <samuraileumas at yahoo.com> > To: Ruben Van Boxem <vanboxem.ruben at gmail.com> > Sent: Wed, January 5, 2011 3:38:21 PM > Subject: Re: [LLVMdev] include/Config/config.h discrepancies between CMake and >autofoo builds > > > >

I don't normally build using nmake.. but I just tried and it worked 100% here. Are you sure you are using the trunk? On Fri, Dec 31, 2010 at 7:32 AM, Ruben Van Boxem <vanboxem.ruben at gmail.com>wrote: > I first sent this to the Clang dev list, but they told me to come here: > > > ---------- Forwarded message ---------- > From: Ruben Van Boxem <vanboxem.ruben at

2010/12/31 Francois Pichet <pichet2000 at gmail.com>: > I don't normally build using nmake.. but I just tried and it worked 100% > here. > Are you sure you are using the trunk? > > On Fri, Dec 31, 2010 at 7:32 AM, Ruben Van Boxem <vanboxem.ruben at gmail.com> > wrote: >> >> I first sent this to the Clang dev list, but they told me to come here:

Hi, Attached is a patch for compiler-rt to allow it to compile with MinGW-w64 on Windows. Results aren't that bad. x86 GCC and Clang do everything right, all tests pass. x86_64 GCC fails a lot of tests. This is 99% sure a codegen issue. 38 - fixunssfti_test (Failed) 74 - fixunsdfti_test (Failed) x86_64 Clang fails these tests: 2 - udivmodti4_test (SEGFAULT) 6 - fixdfti_test (Failed) 8 -

I first sent this to the Clang dev list, but they told me to come here: ---------- Forwarded message ---------- From: Ruben Van Boxem <vanboxem.ruben at gmail.com> Date: 2010/12/31 Subject: LLVM on Windows MSVC 10 To: cfe-dev at cs.uiuc.edu Hi, I'm trying to build svn LLVM with Visual Studio 2010: cd build cmake .. -G"NMake Makefiles" nmake and several link steps fail

On Thu, Oct 6, 2011 at 2:00 PM, Ruben Van Boxem <vanboxem.ruben at gmail.com> wrote: > When building LLVM/Clang, I get the following build failure: > > MinGW-w64 provides the necessary typedefs and declarations. I adjusted the > ifdef's to include a check for a the MinGW-w64-specific symbol of choice to > differentiate mingw.org vs mingw-w64. Tested on i686-w64-mingw32 and

2011/10/6 Aaron Ballman <aaron at aaronballman.com> > On Thu, Oct 6, 2011 at 2:09 PM, Ruben Van Boxem > <vanboxem.ruben at gmail.com> wrote: > > You're welcome! Please remember that MinGW-w64 does not mean it is > 64-bit. > > It provides both 32- and 64-bit headers/libs. The "w64" in the name was > > originally because that was the

On Thu, Oct 6, 2011 at 2:09 PM, Ruben Van Boxem <vanboxem.ruben at gmail.com> wrote: > You're welcome! Please remember that MinGW-w64 does not mean it is 64-bit. > It provides both 32- and 64-bit headers/libs. The "w64" in the name was > originally because that was the project's principal goal, among extending > the API completeness and compatibility with MSVC.

Ruben Van Boxem <vanboxem.ruben at gmail.com> writes: >>> I'm trying to build svn LLVM with Visual Studio 2010: >>> >>> cd build >>> cmake .. -G"NMake Makefiles" >>> nmake >>> >>> and several link steps fail due to a missing symbol: >>> >>> > LLVMX86CodeGen.lib(X86JITInfo.cpp.obj) : error

Ruben, 2011/1/30 Ruben Van Boxem <vanboxem.ruben at gmail.com>: > Can the tools in LLVM create a Win32 exe or dll file? Or does LLVM > still rely on Binutils and GCC for that? Is it > possible/feasable/wanted that the LLVM toolchain could do this? As you know, we need our linker! Please look into the slide in http://llvm.org/devmtg/2010-11/ "Object Files in LLVM" by