Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
29283 Discussions

Turning off Parallel Code Generation

mattsdad
Beginner
‎04-19-2007 08:53 AM
401 Views

I have use the Intel Thread Checker against a run of my simulator, and the only problem identified was a thread stall. The stallbegan in the first 10 seconds of execution, and was reported at 40 seconds. The thread checker did not give any data for the 1st Access. The 2nd Access was in a portion of code that does not need to be parallel.

Is there any way to turn off the automatic parallelization of portions of code outside the OpenMP section? (I could easily let everything ina filebe turned off.)

0 Kudos

Link Copied

1 Reply
TimP
Honored Contributor III
‎04-19-2007 01:02 PM
401 Views
You should not have any threaded parallelism from your own source code, outside OpenMP parallel regions, if you did not invoke -Qparallel or explicit threading. I have had concerns myselfabout a possible false indication from Thread Checker. If you could provide a detailed case, I would suggest filing an issue on your premier.intel.com account.
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.