search for: czhao

...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 `/home/czhao/ResearchTools/LLVM/2.3/obj2.3/lib/System' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/home/czhao/ResearchTools/LLVM/2.3/obj2.3/lib/System' make[1]: Entering directory `/home/czhao/R...

...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 /home/czhao/ResearchTools/LLVM/SubProjects/Safecode/llvm/projects/poolalloc/runtime/DynamicTypeChecks/TypeRuntime.cpp:52: error: integer constant is too large for ‘long’ type /home/czhao/ResearchTools/LLVM/SubProjects/Safecode/llvm/projects/poolalloc/runtime/DynamicTypeChecks/TypeRuntime.cpp:99: error: i...

...(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 eecg.toronto.edu> wrote: > 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...

...m 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 > `/home/czhao/ResearchTools/LLVM/2.3/obj2.3/lib/System' > make[1]: Nothing to be done for `all'. > make[1]: Leaving directory > `/home/czhao/ResearchTools/LLVM/2.3/obj2.3/lib/System' > make[1]: Ente...

Dear All, We have a new release of Clang with SAFECode technology for detecting memory safety errors. Memory safety checking (SAFECode for short) can be turned on with a single command line switch to clang/clang++. The SAFECode techniques do not change the behavior of the clang/clang++ compilers in any way when the switch is turned off, so this can be used as a drop-in replacement for

...e 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 for working C compiler: /steffan/a/a0/czhao/bin/bin32/gcc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works -- Detecting CXX compiler ABI i...

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

...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 >> `/home/czhao/ResearchTools/LLVM/2.3/obj2.3/lib/System' >> make[1]: Nothing to be done for `all'. >> make[1]: Leaving directory >> `/home/czhao/ResearchTools/LLVM/2.3/obj2.3/lib/System'...

...de, but not clear what the problem is. Please let me know what I should do in this case. Thank you Chuck ----------------------------------------------------------------------------------------------- Error msg after typing gmake -k ... ... llvm[1]: Compiling Function.cpp for Release build /home/czhao/LLVM/llvm-2.0/lib/VMCore/Function.cpp:273: error: 'llvm::FunctionTyp e* llvm::Intrinsic::getType(llvm::Intrinsic::ID, const llvm::Type**, uint32_t)' should have been declared inside 'llvm::Intrinsic' make[1]: *** [/home/czhao/LLVM/obj2.0/lib/VMCore/Release/Function.o] Error 1 make...

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

...t; in the sense of aesthetics. :) -Dave ------------------------------ Message: 6 Date: Tue, 22 Feb 2011 12:23:27 -0800 From: Talin <viridia at gmail.com> Subject: Re: [LLVMdev] still failed to build the llbrowse on Debian5-32b-llvm2.8 To: Chuck Zhao <czhao at eecg.toronto.edu> Cc: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> Message-ID: <AANLkTim8icrL_2ga0Bx1UJi8qqtG1KCZo_bcYnE8+x7R at mail.gmail.com> Content-Type: text/plain; charset="iso-8859-1" OK try it now - I checked in a few more fixes. On Tue, Feb 2...

...his case. I believe this has been fixed on mainline CVS, try it. :) -Chris > ----------------------------------------------------------------------------------------------- > Error msg after typing gmake -k > ... > ... > llvm[1]: Compiling Function.cpp for Release build > /home/czhao/LLVM/llvm-2.0/lib/VMCore/Function.cpp:273: error: > 'llvm::FunctionTyp > e* llvm::Intrinsic::getType(llvm::Intrinsic::ID, const llvm::Type**, > uint32_t)' > should have been declared inside 'llvm::Intrinsic' > make[1]: *** [/home/czhao/LLVM/obj2.0/lib/VMCore/Release/F...

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 (-alwa...

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

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

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

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

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

...[run] Error 1 Basically, it can't find the hello pass. However, when I was trying to run the same code under Debian4-i386, I got a totally opposite error: "Passes registered multiple times" opt -load Release/lib/Hello.so -hello < test.bc > /dev/null opt: /autofs/steffan/a/a0/czhao/ResearchTools/LLVM/2.7/llvm-2.7/lib/VMCore/Pass.cpp:234: void<unnamed>::PassRegistrar::RegisterPass(const llvm::PassInfo&): Assertion `Inserted && "Pass registered multiple times!"' failed. 0 opt 0x085e6809 Stack dump: 0. Program arguments: opt -load Release/li...