Hello I spent some time trying to get the test-suite running as per the instructions here: http://www.llvm.org/docs/TestingGuide.html I was continually getting an error "No rule to make target `Output/sse.expandfft.linked.rbc', needed by `Output/sse.expandfft.linked.bc'." Eventually, it turned out that calling configure without setting --with-llvmgccdir and having llvm-gcc in the path worked just fine. Can I suggest that the instruction docs are changed to reflect this? Thanks
On Apr 10, 3:49 pm, Dominic Hamon <dom.ha... at gmail.com> wrote:> HelloHi Dominic!> > I spent some time trying to get the test-suite running as per the > instructions here:http://www.llvm.org/docs/TestingGuide.htmlYep.> > I was continually getting an error "No rule to make target > `Output/sse.expandfft.linked.rbc', needed by > `Output/sse.expandfft.linked.bc'."Same for me, I grew some grey hair with this.> > Eventually, it turned out that calling configure without setting > --with-llvmgccdir and having llvm-gcc in the path worked just fine. Can > I suggest that the instruction docs are changed to reflect this?Since only some privileged people have CVS access, I could not do this myself :-( Sabre, can you *please* reflect this change, so that no more people against this wall? :-) Cheers, Gabor> > Thanks > > _______________________________________________ > LLVM Developers mailing list > LLVM... at cs.uiuc.edu http://llvm.cs.uiuc.eduhttp://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
I would like to make the following target specific modifications to clang and would like to get some advice from experts. 1) My target supports very poor stack access so we implement "static stack". In this model, all local variables will have static storage class. I think I can take care of this in the clang::CGDecl.cpp::CodeGenFunction::EmitBlockVarDecl() 2) To improve memory usage, I also would like to add a new default attribute "overlay" to local variables (all will have static storage class as mentioned in 1). This attribute will be applied to all local variables except if the user has explicitly made the variable static in which case the attribute is not added. I think I should be able to take care of this also in the same place clang::CGDecl.cpp::CodeGenFunction::EmitBlockVarDecl() however I don't know how to define and apply the "overlay" attribute. 3) I did not find any way to access the attributes from llvm backend. I was wondering if I should use something similar to what address space is doing or there may be some other way possible. 4) Input arguments and return value of all functions should also have the same overlay-static storage class. I can take care of these entirely in the backend. However, I would like to know your feedback. Thanks