similar to: [LLVMdev] C-Backend bug

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

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

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

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

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

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

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

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

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

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

Hi Mike-M, Thanks for the help. It seems I'll have to just download the precompiled binaries since I only have 1 Gig in the entire system I'm using. --Sam ----- Original Message ---- > From: mike-m <mikem.llvm at gmail.com> > To: Samuel Crow <samuraileumas at yahoo.com> > Sent: Wed, May 5, 2010 3:36:34 PM > Subject: Re: [LLVMdev] Another bad binutils? >

Hey Chuck, I'm afraid I can't reproduce your error but...a problem you may run into later is that opt will complain with opt: llvm/lib/VMCore/Pass.cpp:149: void<unnamed>::PassRegistrar::RegisterPass(const llvm::PassInfo&): Assertion `Inserted && "Pass registered multiple times!"' failed. Aborted I "fixed" this by replacing the LLVMLIBS line in

----- Original Message ---- > From: Óscar Fuentes <ofv at wanadoo.es> > To: Samuel Crow <samuraileumas at yahoo.com> > Cc: Óscar Fuentes <ofv at wanadoo.es>; LLVM Developers Mailing List ><llvmdev at cs.uiuc.edu> > Sent: Fri, January 14, 2011 4:39:57 PM > Subject: Re: Circular Deps from CMake build using makefile > > Samuel Crow <samuraileumas

Thanks, Shu, I guess I haven't updated since my post went out. There are actually 2 problems: 1. mis-compilation: My LLVM-2.5 turned out to be mis-compiled using gcc-4.4.0 (surprise to me) on Debian4-32b. I tried a few different compilers, and gcc-4.0.4 (a relatively old one, again surprised me) seems to work out fine. Question: is there a good/quick/reliable way to figure out whether a

Hello Óscar, This time the autotools version of LLVM trunk build with Clang trunk compiled in Debug+Asserts mode without complaint with --enable-bindings=none. I suspect this makes something fishy looking with the CMake build. Do you need logfiles from configure? Thanks again, --Sam ----- Original Message ---- > From: Óscar Fuentes <ofv at wanadoo.es> > To: Samuel Crow