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.
29280 Discussions

How to get Number of Processors

chrisquan
Beginner
‎05-09-2002 05:32 PM
1,345 Views
I was told that in Compaq Visual Fortran, the internal function "Number_of_Processors" is always returned to 1 on Windows even for multi-processor machines. Does anybody know if there are the third party software to get around this?
0 Kudos

Link Copied

2 Replies
james1
Beginner
‎05-09-2002 07:12 PM
1,345 Views
Don't know why that intrinsic wouldn't work but it is easy enough to replace:
use kernel32
type (T_SYSTEM_INFO) si
call GetSystemInfo (si)
! number of processors is in si%dwNumberOfProcessors

James
0 Kudos
Copy link
Steven_L_Intel1
Employee
‎05-09-2002 08:46 PM
1,345 Views
NUMBER_OF_PROCESSORS is an intrinsic that's part of HPF (High-Performance Fortran), a feature provided by Compaq only on Tru64 UNIX. Our implementation is to return a 1 on all platforms other than Tru64 UNIX, as that's the only platform where we support multiprocessing directly in the compiler.

The documentation is misleading about this and we'll fix it. Sure, we could change the intrinsic to ask the OS how many processors are present, but it's really meant to inquire about HPF parallelism capability.

Steve
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.