Thomas Heller <thomas.hell...@gmx.de> writes: > I ran into a little issue when trying to force inlining with > __attribute__(( always_inline )). The reason why i am trying to force > the compiler to inline my code is simple: I want to implement handwritten > optimizations using SSE intrinsics. However it seems that gcc is not willing > to inline that code anymore. That is why i came up with the idea of trying to > force gcc. > There is a problem now. I get tons of error messages that gcc is not able to > inline that function. > Example error message: > sorry, unimplemented: inlining failed in call to ‘const pe::Vector3<typename > pe::MathTrait<T1, T2, true>::AddType> pe::operator+(const pe::Vector3<Type>&, > const pe::Vector3<T2>&) [with T1 = double, T2 = double]’: function not > inlinable > > I was trying to put that in a little testcase. However it seems that i can't > reproduce that error with a small code base. > Any ideas? Need more information?
This question is not appropriate for the gcc@gcc.gnu.org mailing list. It would be appropriate for gcc-h...@gcc.gnu.org. Please take any followups to gcc-help. Thanks. Unfortunate, it's basically impossible for us to say anything useful without some sort of test case. I assume you are using the SSE intrinsics from mmintrin.h and friends. Those intrinsics should be reliably inlined. Why is it necessary for you to inline them further? For whatever it's worth, the development version of gcc gives better messages about why a function can not be inlined. Ian
