<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to Timer Control</title><link>https://sourceforge.net/p/ichnaea/wiki/Timer%2520Control/</link><description>Recent changes to Timer Control</description><atom:link href="https://sourceforge.net/p/ichnaea/wiki/Timer%20Control/feed" rel="self"/><language>en</language><lastBuildDate>Wed, 29 Jan 2014 11:35:33 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/ichnaea/wiki/Timer%20Control/feed" rel="self" type="application/rss+xml"/><item><title>Timer Control modified by Iain Miller</title><link>https://sourceforge.net/p/ichnaea/wiki/Timer%2520Control/</link><description>&lt;div class="markdown_content"&gt;&lt;h2 id="timer-control"&gt;Timer Control&lt;/h2&gt;
&lt;p&gt;The following routines are used to control the state of the timers. A timer must be started and stopped for a timing block to be counted and can only be paused after it has been started and continued after it has been paused for the time to be valid. These states are not checked in the optimised version but there is a debug version available in which these states are checked and any erroneous states are reported.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;OpenMP:&lt;/strong&gt; Once created, timers provide no thread protection mechanisms such that no two threads should access the same timer at the same time. If multiple access is needed a serialisation mechanism like a barrier or critical region should separate the actions.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Iain Miller</dc:creator><pubDate>Wed, 29 Jan 2014 11:35:33 -0000</pubDate><guid>https://sourceforge.net158de9236c6e771b39ba422cc6a0510995fb4a8b</guid></item></channel></rss>