similar to: [LLVMdev] published a copy of Cygwin frontend binary

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 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 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

I am trying to build LLVM 2.0 (source downloaded from llvm.org) under WinXP/Cygwin, and got compilation errors. I have tried to use: GCC 3.4.4. GCC 4.0.4 GCC 4.1.2 and GCC 4.2.0, and the error remains. I looked at the code, but not clear what the problem is. Please let me know what I should do in this case. Thank you Chuck

I sent an earlier email about failing to compile 4.2, I have since tried 4.0 and I get a configure error during make. I am running on windows XP SP2 Cygwin is (as reported by uname -a): CYGWIN_NT-5.1 pad7 1.5.25(0.156/4/2) 2007-12-14 19:21 i686 Cygwin Gcc is: gcc (GCC) 3.4.4 (cygming special, gdc 0.12, using dmd 0.125) I ran configure, then make. Make dies with: checking whether the C

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]:

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

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

Dear llvmdev, I am new to LLVM , but have a task on writing a LLVM backend to generate some architecture specific assembly file. Here is my cygwin build setting: GCC 3.4.4 , BIN UTILITY 2.15 ,and all other packages of the right version listed on the LLVM Getting Started doc. I have successfully built Release 1.6 LLVM. All the tools has been installed there /usr/local/bin . But I

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

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

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

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

Hi, I'm trying to build LLVM 2.6 (from svn branch release_26) on cygwin 1.7, and I have the following errors with both GCC 3.4.4 and GCC 4.3.4 llvm[2]: Linking Release Loadable Module profile_rt.dll /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld: warning: cannot find entry symbol __cygwin_dll_entry at 12; defaulting to 62fc1000

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 "always_inline" attribute. They are both subclasses of Inline.cpp that assumes the function's definition (body) is

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

> 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. :) Weird, I built it on 3.4.4 on testing for release ? Aaron

LLVMers, I need to intercept all LLVM IR instructions that will write into memory and start to do analysis on these instructions. In addition to StoreInst, what are all other IRs that will write into memory? E.g. char * ptr = malloc(...); ///... //with use(s) of ptr later The LLVM IR for the above code would be: %0 = tail call noalias i8* @malloc(i32 137) nounwind ///... //