Hi! > I saw that "Change add to a static inline function. > This is usually the right solution if only one translation > unit needs to use the function. static inline functions are > always resolved within the translation unit, so you won't have > to add a non-inline definition of the function elsewhere in your program." > > So, why not just change it to "static inline" to resolve this?
Interestingly enough, the function is passed via pointer so compiler couldn't inline it at all, I wonder why there was the inline in the first place... I've removed the inline added static and confirmed that it builds with clang 3.1 on x86_64. -- Cyril Hrubis [email protected] ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
