<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: sport commands in a threaded application in Intel® Fortran Compiler</title>
    <link>https://community.intel.com/t5/Intel-Fortran-Compiler/sport-commands-in-a-threaded-application/m-p/815085#M44830</link>
    <description>For a complete module illustrating serial i/o in a multithreaded Win32 environment, written with Win32 API calls instead of the sport routines, please send an email request.&lt;BR /&gt;Paul Curtis&lt;BR /&gt;pcurtis@kiltel.com</description>
    <pubDate>Mon, 07 Apr 2003 23:03:50 GMT</pubDate>
    <dc:creator>pcurtis</dc:creator>
    <dc:date>2003-04-07T23:03:50Z</dc:date>
    <item>
      <title>sport commands in a threaded application</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/sport-commands-in-a-threaded-application/m-p/815083#M44828</link>
      <description>Hi,&lt;BR /&gt;I have written a multithreaded serial communication application and it uses the functions outp and inp to communicate with the COM1 port. Recently I went about converting my code into calls using sport_read_line and sport_write_line instead of outp and inp. However I notice that the sport routine does not work well in a multithreaded case. As soon as I create a thread erroneous values are returned by the sport command. Do you have any pointers on how to make the sport commands function in a multithreaded case. Thanks,&lt;BR /&gt;-hcra</description>
      <pubDate>Mon, 07 Apr 2003 13:39:02 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/sport-commands-in-a-threaded-application/m-p/815083#M44828</guid>
      <dc:creator>hcra</dc:creator>
      <dc:date>2003-04-07T13:39:02Z</dc:date>
    </item>
    <item>
      <title>Re: sport commands in a threaded application</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/sport-commands-in-a-threaded-application/m-p/815084#M44829</link>
      <description>From what I see in the documentation, using the SPORT routines in a multithreaded application should work.  However, the documentation does say "To help ensure that data overruns do not occur, the SPORT_xxx run-time support creates a separate thread that maintains an outstanding read to the connected port. This thread is started when any read or write operation is performed to the port using the affiliated read/write routine. As such, port parameters must not be changed after you have started reading or writing to the port. Instead, you should set up the port parameters after connecting to the port and then leave them unchanged until after the port has been released."&lt;BR /&gt;&lt;BR /&gt;If you can come up with a simple example that fails, and are using CVF 6.6B. please feel free to send it to vf-support@compaq.com&lt;BR /&gt;&lt;BR /&gt;Steve</description>
      <pubDate>Mon, 07 Apr 2003 22:27:50 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/sport-commands-in-a-threaded-application/m-p/815084#M44829</guid>
      <dc:creator>Steven_L_Intel1</dc:creator>
      <dc:date>2003-04-07T22:27:50Z</dc:date>
    </item>
    <item>
      <title>Re: sport commands in a threaded application</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/sport-commands-in-a-threaded-application/m-p/815085#M44830</link>
      <description>For a complete module illustrating serial i/o in a multithreaded Win32 environment, written with Win32 API calls instead of the sport routines, please send an email request.&lt;BR /&gt;Paul Curtis&lt;BR /&gt;pcurtis@kiltel.com</description>
      <pubDate>Mon, 07 Apr 2003 23:03:50 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/sport-commands-in-a-threaded-application/m-p/815085#M44830</guid>
      <dc:creator>pcurtis</dc:creator>
      <dc:date>2003-04-07T23:03:50Z</dc:date>
    </item>
  </channel>
</rss>

