<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<atom:link href="http://www.multicorebsp.com/forum/extern.php?action=feed&amp;fid=11&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[The MulticoreBSP Forums / Bug reports]]></title>
		<link>http://www.multicorebsp.com/forum/index.php</link>
		<description><![CDATA[The most recent topics at The MulticoreBSP Forums.]]></description>
		<lastBuildDate>Sun, 11 Nov 2012 11:36:30 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[Bug? Global memory corrupted after bsp_sync() [not-a-bug]]]></title>
			<link>http://www.multicorebsp.com/forum/viewtopic.php?id=21&amp;action=new</link>
			<description><![CDATA[<p>If it&#039;s searching for a position only (no changes to the tree), then passing the global variables as const parameters should already stop the compiler from pushing them onto the stack after each recursive call <img src="http://www.multicorebsp.com/forum/img/smilies/wink.png" width="15" height="15" alt="wink" /></p><p>It generally also helps performance to store tree-like structures in flat arrays, and transform recursive algorithms into loop-based ones (to help data locality and prevent pushing return addresses at each recursion, respectively); if your application allows such changes of course..</p><p>In any case, I hope the changes are not hard to incorporate,<br />and don&#039;t hesitate to post again if BSP issues seem to pop up! <img src="http://www.multicorebsp.com/forum/img/smilies/smile.png" width="15" height="15" alt="smile" /></p>]]></description>
			<author><![CDATA[dummy@example.com (Albert-Jan Yzelman)]]></author>
			<pubDate>Sun, 11 Nov 2012 11:36:30 +0000</pubDate>
			<guid>http://www.multicorebsp.com/forum/viewtopic.php?id=21&amp;action=new</guid>
		</item>
	</channel>
</rss>
