Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
29276 Discussions

Is there any run-time penalty related to the use of ASSOCIATE constructs?

OP1
New Contributor III
‎09-02-2009 07:14 AM
310 Views
I am taking the plunge into the wonderful world of IVF 11.1... At last...

Among all the very exciting new features of IVF 11.1 the ASSOCIATE construct seems to be of great benefit for my code. I manipulate many complicated structures with nested derived type components. So I end up with variables which look like A(10)%B(1:3)%C(25)%D.

Hereis my question: It seems that ASSOCIATE(xxx => yyy) ismostly a convenient syntactic feature that helps make a code more manageable (easy to write/understand); but there is probably more than meet the (my) eye here and I am wondering ifthere isa penalty to pay for this at run time; or if the ASSOCIATE construct is *compiled out* when compiling the application.

Thanks in advance for shedding some light on this topic,

Olivier
0 Kudos

Link Copied

1 Reply
Steven_L_Intel1
Employee
‎09-02-2009 07:51 AM
310 Views

Not that I can think of. It's primarily dealt with at compile-time. Offhand, I don't know of any extra run-time overhead for it.
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.