search for: stripllvmtranslationfn

...nvert.cpp:344: warning: statement with no effect ../../2006-03-02-llvm-gcc-4/gcc/llvm-convert.cpp: At global scope: ../../2006-03-02-llvm-gcc-4/gcc/llvm-convert.cpp:1305: error: parse error before `__attribute__' ../../2006-03-02-llvm-gcc-4/gcc/llvm-convert.cpp: In function `tree_node* StripLLVMTranslationFn(...)': ../../2006-03-02-llvm-gcc-4/gcc/llvm-convert.cpp:1312: error: `I' undeclared (first use this function) ../../2006-03-02-llvm-gcc-4/gcc/llvm-convert.cpp:1312: error: (Each undeclared identifier is reported only once for each function it appears in.) ../../2006-03-02-llvm-gcc-4/g...

....cpp:1305: error: parse error > before `__attribute__' Can you send me the preprocessed .i file for this file? To work around the above error, just remove "ATTRIBUTE_UNUSED" from that line. > ../../2006-03-02-llvm-gcc-4/gcc/llvm-convert.cpp: In function `tree_node* > StripLLVMTranslationFn(...)': > ../../2006-03-02-llvm-gcc-4/gcc/llvm-convert.cpp:1312: error: `I' undeclared > (first use this function) > ../../2006-03-02-llvm-gcc-4/gcc/llvm-convert.cpp:1312: error: (Each > undeclared > identifier is reported only once for each function it appears in.) > ....

...d .i file for this file? Sure, I've sent it by private email (180K is too big for list). > To work around the above error, just remove "ATTRIBUTE_UNUSED" from that > line. Ok, done. >> ../../2006-03-02-llvm-gcc-4/gcc/llvm-convert.cpp: In function `tree_node* >> StripLLVMTranslationFn(...)': >> ../../2006-03-02-llvm-gcc-4/gcc/llvm-convert.cpp:1312: error: `I' >> undeclared >> (first use this function) >> ../../2006-03-02-llvm-gcc-4/gcc/llvm-convert.cpp:1312: error: (Each >> undeclared >> identifier is reported only once for each fu...

On Thu, 2 Mar 2006, Chris Lattner wrote: >> Any ideas what could be wrong? > > Sorry for the delay, please try this tarball: > http://nondot.org/sabre/2006-03-02-llvm-gcc-4.tar.gz Actually, do to a recent change in CVS, this tarball will probably not work anymore. Please apply the attached (small) patch on top of it in the gcc directory. Worth noting, this front-end only works

On Thu, 2 Mar 2006, Vladimir Prus wrote: >>> The instructions seem to have one path wrong. It says to get: >> >> I'll put together a tarball today. That will be easier than dealing with >> a patch, and it will include a bunch of bugfixes since the previous email. > Further into process, I get this error: > In file included from