search for: shukang

...2VBS.s", line 3147: error: cannot use v8plus registers in a non-v8plus target binary ... ------------- There are 42 similar errors in this file ("cannot use v8plus registers in a non-v8plus target binary"). Is anyone who knows about this error? Thanks a lot for your time and help. Shukang Zhou

Thanks Misha. I tried the "gcc -dM -E /tmp/file.c | grep __sparcv9" but there was no output. Maybe this is the probelm, I do have CXX = g++ -mcpu=v9 CC := gcc -mcpu=v9 in the Makefile.config. Do I need to add -m64 as well? Thanks. Shukang On Thu, 7 Oct 2004, Misha Brukman wrote: > Is your compiler configured to define __sparcv9 when it compiles? > The following should tell you: > > % touch /tmp/file.c > % gcc -dM -E /tmp/file.c | grep __sparcv9 > > If the output is similar to the below, you're fine: > #...

...and found that it crashes within JIT::runFunction(). In particular, the problem is in line 70 of JIT.cpp: int ExitCode = PF(ArgValues[0].IntVal, (char **) GVTOP (ArgValues[1]), (const char **) GVTOP (ArgValues[2])); Is anybody having any idea about this? Thanks a lot. Shukang Zhou

On Thu, Oct 07, 2004 at 06:22:34PM -0400, Shukang Zhou wrote: > I am working with llvm 1.3 on a sparcv9 machine. I have successfully > built llvm and llvm-gcc frontend. I can run many tools including > llvmgcc, llvm-dis, and llc. After using /opt/SUNWspro/bin/cc to > assemble .s file into a program binary, I can run the binary correctl...

On Thu, Oct 07, 2004 at 06:46:18PM -0400, Shukang Zhou wrote: > Thanks Misha. I tried the "gcc -dM -E /tmp/file.c | grep __sparcv9" > but there was no output. Maybe this is the probelm, I do have > > CXX = g++ -mcpu=v9 > CC := gcc -mcpu=v9 > > in the Makefile.config. Do I need to add -m64 as well? Thanks. Just run...

I'm sorry, I did not completely understand your email, let me clarify my response. On Thu, Oct 07, 2004 at 06:46:18PM -0400, Shukang Zhou wrote: > Thanks Misha. I tried the "gcc -dM -E /tmp/file.c | grep __sparcv9" > but there was no output. Maybe this is the probelm, I do have > > CXX = g++ -mcpu=v9 > CC := gcc -mcpu=v9 > > in the Makefile.config. Do I need to add -m64 as well? Thanks. Just run...

...to original LLVM bytecode? 4. What runtime optimizations are applied in the current version? Would it be possible to provide a more detailed document? If not convenient, please give us a brief description of files which are in charge of these functions. I appreciate your effort and time. Thanks. Shukang Zhou

...How should I deal with this? I checked tools/Debug, and many tools' binary has been generated, including gccas, gccld, llc, lli, opt, etc. I wonder what is the functionality of profile_rt. Plus, if my "gmake" stops at profile_rt, what are the components in LLVM I cannot use? Thanks. Shukang Zhou

On Wed, 6 Oct 2004, Reid Spencer wrote: > This file (UnixLocalInferiorProcess.cpp) is due for porting and placement in > lib/System but I haven't gotten there yet. If you come up with something that > works on MINGW, please let me know. As you might guess by the name, this file is essentially entirely unix specific. The debugger is designed so that multiple backends can be plugged

On Wed, Sep 29, 2004 at 06:44:50PM -0400, Shukang Zhou wrote: > I met some errors when I tried to build LLVM. The tar file is > llvm-1.3.tar.gz. I am using a sparc machine with gcc 3.2.2. > > ------------- > Compiling SparcV9CodeEmitter.cpp > /uf24/zhou/research/llvm/src/lib/Target/SparcV9/SparcV9CodeEmitter.cpp: In > stat...