search for: ymxia

ymxia at nudt.edu.cn wrote: > When I compiled a linux kernel, gccas was used to compile assembly code. > > But gccas cannot recognize the line comment character "#" of gnu assembler, > > and abort the compile with reporting a error "syntax error, unexpected $undefined&quo...

When I compiled a linux kernel, gccas was used to compile assembly code. But gccas cannot recognize the line comment character "#" of gnu assembler, and abort the compile with reporting a error "syntax error, unexpected $undefined". I watch llvm/tools/gccas, but donot known how to add this function in it. Would you give me some suggestions? Thanks.

ymxia at nudt.edu.cn wrote: > Hi, > > I want to check some properties of linux kernel with llvm, but I don't know how to compile a > > linux kernel to an llvm's .bc file. I have let llvm's gcc front-end ignore inline assembly by > > modifying cfrontend/src/gcc/llvm...

Hi, I want to check some properties of linux kernel with llvm, but I don't know how to compile a linux kernel to an llvm's .bc file. I have let llvm's gcc front-end ignore inline assembly by modifying cfrontend/src/gcc/llvm-expand.c, and replace CC/as/ar in the Makefile of the kernel with llvm-gcc/llvm-as/llvm-ar. However, the linux's "make" reports errors:

...gt; > >_______________________________________________ >LLVM Developers mailing list >LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev = = = = = = = = = = = = = = = = = = = = 　　　　　　　　致 礼！ 　　　　　　　　Yimin Xia 　　　　　　　　ymxia at nudt.edu.cn 　　　　　　　　　　2006-03-26

...ot &p = &q. Another question is about "forwarding". "AliasSet[XXXX, 0] may alias, Mod/Ref forwarding to YYYY" (XXXX != YYYY) means the address XXXX can be regarded as YYYY in interprocedural analysis, and XXXX should be ignored? Thank you. >On Sat, 14 Jan 2006, ymxia wrote: >> 1. The following is the primary body of my pass "fps.cpp": >> >> AliasAnalysis *AA = &getAnalysis<AliasAnalysis>(); >> AliasSetTracker AST(*AA); >> >> for (Module::iterator fi = M.begin(), fe = M.end(); fi != fe; ++fi ) >>...

Thank you, Chris. The following is my comprehension about the AliasSetTracker, please correct me. 1. A aliasset "as" represents a memory object, and all pointer "p" in "as" represent values with the type of pointer that may/must point to the memory object "as". 2. If a aliasset is "forwarding", it has been merged to another aliasset and I

>On Monday 22 May 2006 22:22, Andrew Lenharth wrote: > The BasicCallGraph class only lines out the indirect calls(makes the caller point to external node), >but do not resolves them using alias analysis such as DSA. >I think DSA solve this problem for interested call sites by finding the corresponding globals(i.e. the functions) >for the callsite DSnode. Yes, if we want to

Hello, I got a strange result when I used alias analysis DSAA, can you tell what is wrong? 1. The following is the primary body of my pass "fps.cpp": AliasAnalysis *AA = &getAnalysis<AliasAnalysis>(); AliasSetTracker AST(*AA); for (Module::iterator fi = M.begin(), fe = M.end(); fi != fe; ++fi ) for (Function::iterator bi = fi->begin(), be = fi->end(); bi

The follwing is a snippet of code to find some indirect calls in a module, which I learned from TopDownClosure.cpp: void FPS::repairCallGraph(Module &M) { CompleteBUDataStructures &DS = getAnalysis<CompleteBUDataStructures>(); for (Module::iterator f = M.begin(); f != M.end(); ++f ) { if( f->isExternal() ) continue; for (Function::iterator I = f->begin(); I !=