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.
Success! Subscription added.
Success! Subscription removed.
Sorry, you must verify to complete this action. Please click the verification link in your email. You may re-send via your
profile.
REAL::X(100,5)
INTEGER::IS,K
IS=merge(MINLOC(X(:,K)),MAXLOC(X(:,-K)),K>0)
! its equivalent is
IF(K>0)THEN
IS=MINLOC(X(:,K))
ELSEIF(K<0)THEN
IS=MAXLOC(X(:,-K))
END IF
Did you mean to set a DIM argument for minloc and maxloc? Until the code does what you intend, talking about efficiency seems pointless.
The strength of MERGE is not for cases as complicated as array operations. Performance would depend on the expansion of minloc and maxloc and whether the compiler is able to optimize without making temporary arrays. The size you quote is marginal on whether vectorization would be useful, and that depends (with recent released ifort) on whether you have set the old_maxminloc. What do your optreports say?
