search for: flagwise

...t;> Just to make sure I understand how LLVM works, got a few >> clarifications: >> >> 1. The ppc code I'm generating with the -native-cbe is static, >> correct? > > Yes, it's purely static with the -native-cbe or -native options. Is there anything special flagwise that I would need to specify to tell it to include symbol and debug information? I've tried specifying -g but this information still doesn't seem to be included. A quick copy of the build of one of the tests to make sure I've got the flags right: Compiling Binaries Building 164.g...

On Sun, 2 May 2004, Patrick Flanagan wrote: > Is there anything special flagwise that I would need to specify to tell > it to include symbol and debug information? I've tried specifying -g > but this information still doesn't seem to be included. A quick copy of > the build of one of the tests to make sure I've got the flags right: Nope. Right now LLVM do...

...rofiled that new code, it still had those two functions in the profile. Does LLVM support inlining (or am I am idiot and tried to do it manually wrong)? Patrick On May 2, 2004, at 10:40 PM, Chris Lattner wrote: > On Sun, 2 May 2004, Patrick Flanagan wrote: >> Is there anything special flagwise that I would need to specify to >> tell >> it to include symbol and debug information? I've tried specifying -g >> but this information still doesn't seem to be included. A quick copy >> of >> the build of one of the tests to make sure I've got the flags...

...el C code, and I'm not convinced that GCC is doing a very good job (ie, without syntactic loops). Please let me know what you find! -Chris > On May 2, 2004, at 10:40 PM, Chris Lattner wrote: > > > On Sun, 2 May 2004, Patrick Flanagan wrote: > >> Is there anything special flagwise that I would need to specify to > >> tell > >> it to include symbol and debug information? I've tried specifying -g > >> but this information still doesn't seem to be included. A quick copy > >> of > >> the build of one of the tests to make sure...

On Fri, 30 Apr 2004, Patrick Flanagan wrote: > Thanks! Grabbed the latest from CVS and added that linker option to the > config file. It looks like it compiles and runs the SPEC tests ok now. Great! > Just to make sure I understand how LLVM works, got a few clarifications: > > 1. The ppc code I'm generating with the -native-cbe is static, correct? Yes, it's purely static

> > There are two problems with this: 1) there is no JIT for PPC yet, so > LLVM will use the interpreter (which is intolerably slow and has other > issues). 2) Spec compiles the executables in one place and them moves > them to another, but it only copies the shell script and not the > bytecode file, so you get that error message. > > The normal solution to this problem