similar to: [LLVMdev] fail to build LLVM 2.0 on Cygwin/WinXP

On Tue, 19 Jun 2007, Chuck Zhao wrote: > I looked at the code, but not clear what the problem is. > Please let me know what I should do in this case. I believe this has been fixed on mainline CVS, try it. :) -Chris > ----------------------------------------------------------------------------------------------- > Error msg after typing gmake -k > ... > ... > llvm[1]:

I used to be able to build LLVM (from source) under Cygwin for llvm-2.2 and previous releases, but can't continue the trend since the release of LLVM 2.3. I have tried a wide variety of gcc compilers (gcc 3.4.4, 4.1.2, 4.2.4 and 4.3.2) on cygwin, they all fail at the same location: C:\cygwin\home\czhao\ResearchTools\LLVM\2.3\obj2.3>make make[1]: Entering directory

On Mon, Oct 06, 2008 at 08:12:05PM -0400, Chuck Zhao wrote: > I used to be able to build LLVM (from source) under Cygwin for llvm-2.2 > and previous releases, but can't continue the trend since the release of > LLVM 2.3. > I have tried a wide variety of gcc compilers (gcc 3.4.4, 4.1.2, 4.2.4 > and 4.3.2) on cygwin, they all fail at the same location: > >

I still can't build LLBrowse on my Debian5-i386 machine today, The following is a full build console output. I am using LLVM-2.8 release build, with needed wxWidgets and CMake. Thank you Chuck sideshow.eecg>time cmake ../llbrowse -- The C compiler identification is GNU -- The CXX compiler identification is GNU -- Check for working C compiler: /steffan/a/a0/czhao/bin/bin32/gcc -- Check

OK try it now - I checked in a few more fixes. On Tue, Feb 22, 2011 at 8:29 AM, Chuck Zhao <czhao at eecg.toronto.edu> wrote: > I still can't build LLBrowse on my Debian5-i386 machine today, > The following is a full build console output. > I am using LLVM-2.8 release build, with needed wxWidgets and CMake. > > Thank you > > Chuck > > sideshow.eecg>time

Hi, My apologies for the trouble. I've disabled building DynamicTypeChecks for now (r138224) and now it builds cleanly on 32bit for me here. As for SAFECode support for 32bit vs 64bit, I believe 32bit should work just fine although I haven't personally tested this. Let me know if you have any further issues/questions. ~Will On Sun, Aug 21, 2011 at 9:26 AM, Chuck Zhao <czhao at

John, The release source code (sc-main.tar) won't compile cleanly under Debian6-i386 (gcc/g++: 4.4.5). The compiler back trace is attached. Please fix it/them and repost. Or, 64b system is a requirement? Thank you Chuck llvm[4]: Compiling TypeRuntime.cpp for Release+Asserts build (PIC) cc1plus: warnings being treated as errors

I am trying to run the HELLO LLVM Pass under WinXP/MinGW, by following the precise steps available at http://www.llvm.org/docs/WritingAnLLVMPass.html. The pass failed to run, giving me the following error: opt -load Release/lib/Hello.dll -hello < ./hello.bc > /dev/null opt.exe: Unknown command line argument '-hello'. Try: 'C:\MSYS\opt\llvm-2.7\bin\opt.exe -help' make:

On 7/27/2010 12:40 PM, Devang Patel wrote: > On Tue, Jul 27, 2010 at 7:46 AM, Chuck Zhao<czhao at eecg.toronto.edu> wrote: >> LLVM (2.7 release version) provides 2 implementations for inlining >> function callsites: >> >> - InlineSimple.cpp (-inline): inline simple callsites >> according to its cost analysis >> - InlineAlways.cpp

Please unsubscribe me from this list. Sujatha Gurumurthy Staffing Consultant/Talent Advisor UMG - Ultra Mobile Group sujatha.gurumurthy at intel.com US ERP Manager Interested in Employee Referral Program Visit referral.intel.com/ Intel USA Employee Referral Program Group 100 Best Companies to Work For 2011: Intel - INTC - from FORTUNE -----Original Message----- From: llvmdev-bounces at

Julien Lerouge wrote: > On Mon, Oct 06, 2008 at 08:12:05PM -0400, Chuck Zhao wrote: > >> I used to be able to build LLVM (from source) under Cygwin for llvm-2.2 >> and previous releases, but can't continue the trend since the release of >> LLVM 2.3. >> I have tried a wide variety of gcc compilers (gcc 3.4.4, 4.1.2, 4.2.4 >> and 4.3.2) on cygwin, they

On Tue, Jul 27, 2010 at 9:46 AM, Chuck Zhao <czhao at eecg.toronto.edu> wrote: > I don't, and the compiler doesn't neither, that is the problem, unless I do > hacking at compile time. > E.g.: > - put all such function's definitions into file1.c > - force to compile file1.c 1st. > - when compiling file2.c: >  . read file1.bc >  . attach to file2's

On Wed, Jan 5, 2011 at 7:03 PM, Chuck Zhao <czhao at eecg.toronto.edu> wrote: > LLVMers, > > I need to intercept all LLVM IR instructions that will write into memory and > start to do analysis on these instructions. ... > Does that mean any LLVM IR that has a valid result field will be able to > store the result into memory? Yes, if the value ends up getting spilled to the

On Tue, Jul 27, 2010 at 7:46 AM, Chuck Zhao <czhao at eecg.toronto.edu> wrote: >  LLVM (2.7 release version) provides 2 implementations for inlining > function callsites: > > - InlineSimple.cpp (-inline):               inline simple callsites > according to its cost analysis > - InlineAlways.cpp (-always-inline):  inline all callsites that are > marked with

I am using LLVM 2.5 release, together with llvm-gcc4.2-2.5. For the hello.c demo testing found close to the end of the GettingStarted document: #include <stdio.h> int main() { printf("hello world\n"); return 0; } Following the instructions: obtaining the bc file: /llvm-gcc -O3 -emit-llvm hello.c -c -o hello.bc/ running through lli: * */lli hello.bc/ I got this

Hi there i'm trying to build LLVM2.0 (enabled-optimized) on Cygwin/x86, gcc version is 4.0.2. Do you have any suggestions for a Cygwin build? Here follows the error log: make[1]: Entering directory `/cygdrive/c/Temp/devtools/llvm-build/lib/VMCore' llvm[1]: Compiling Function.cpp for Release build /cygdrive/c/Temp/devtools/llvm-2.0/lib/VMCore/Function.cpp:272: error: 'const

On Sat, Feb 19, 2011 at 12:27 PM, Talin <viridia at gmail.com> wrote: > LLBrowse - a GUI tool which allows you to inspect the contents of LLVM > modules - now runs on Linux and OS X, and it works with both LLVM 2.8 and > current LLVM head. I've updated the docs to include instructions on checking > out and building the code under several different environments, which you

LLBrowse - a GUI tool which allows you to inspect the contents of LLVM modules - now runs on Linux and OS X, and it works with both LLVM 2.8 and current LLVM head. I've updated the docs to include instructions on checking out and building the code under several different environments, which you can read here: http://llvm.org/svn/llvm-project/llbrowse/trunk/doc/LLBrowse.html (the doc also

I don't think licm looks at loads/stores to allocas -- these are usually handled by mem2reg which happens much earlier (if you run your example with -mem2reg you'll see it already deleted the store). In fact, licm sinks the stores by converting them to stores to allocas first and running mem2reg on that. If you change your example to void testLICM(int* restrict p) { int i,N=100;

I think the problem is also platform dependent, and I have been trying to come up with the known-good list of build gcc/g++ on various platforms for a long time. E.g., on Debian-32 5.0.5 (Intel): gcc-4.0.4, gcc-4.1.2 are bad, gcc-4.2.4 seems to be fine. on Debian-64 5.0.4 (Intel): the default gcc (4.3.2) seems to be fine. We may want to cover this for a wide range of possible platforms. The