Boost C++ Libraries: Ticket #9169: Make Boost.Ref use BOOST_FORCEINLINE for better performance https://svn.boost.org/trac10/ticket/9169 <p> boost::ref is used a lot to build expression templates or function objects which typically need to be inlined to get decent performance. </p> <p> Using BOOST_FORCEINLINE ensures that it does get inlined, even when minimal inlining options are used. </p> <p> It is very important to do this to get acceptable performance in debug for some the of the libraries I work on, like Boost.SIMD or NT². </p> <p> See the attached patch. </p> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/9169 Trac 1.4.3 Mathias Gaunard Fri, 27 Sep 2013 17:16:20 GMT attachment set https://svn.boost.org/trac10/ticket/9169 https://svn.boost.org/trac10/ticket/9169 <ul> <li><strong>attachment</strong> → <span class="trac-field-new">boost_ref_forceinline.diff</span> </li> </ul> <p> patch to add BOOST_FORCEINLINE to critical boost::ref functions </p> Ticket Joel Falcou Tue, 01 Oct 2013 15:02:29 GMT status changed; resolution set https://svn.boost.org/trac10/ticket/9169#comment:1 https://svn.boost.org/trac10/ticket/9169#comment:1 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">fixed</span> </li> </ul> <p> (In <a class="changeset" href="https://svn.boost.org/trac10/changeset/86124" title="Fix #9169 - Add BOOST_FORCEINLINE on boost::ref for performance issue ">[86124]</a>) Fix <a class="closed ticket" href="https://svn.boost.org/trac10/ticket/9169" title="#9169: Bugs: Make Boost.Ref use BOOST_FORCEINLINE for better performance (closed: fixed)">#9169</a> - Add BOOST_FORCEINLINE on boost::ref for performance issue </p> Ticket Peter Dimov Tue, 01 Oct 2013 15:34:28 GMT <link>https://svn.boost.org/trac10/ticket/9169#comment:2 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/9169#comment:2</guid> <description> <p> I tend to only close tickets when the fixes are in the release branch in addition to trunk, because this helps me remember to merge. </p> </description> <category>Ticket</category> </item> </channel> </rss>