This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Tobias Burnus wrote:Daniel Kraft wrote:* What's the usage of EXEC_ASSIGN_CALL instead of EXEC_CALL?It was introduced with PR25746 - and there with the patch "[Patch, fortran] PR25746 - operator assignment dependency checking", http://gcc.gnu.org/ml/gcc-patches/2006-05/msg00296.html.
That patch introduces the distinction in gfc_trans_call whether a dependency checking should be done (EXEC_ASSIGN_CALL) or not (EXEC_CALL).
Hm, I still don't get the difference between EXEC_ASSIGN_CALL and EXEC_CALL. Shouldn't writing the ASSIGNMENT(=) operator and calling the assignment-procedure directly in the code be exactly equivalent? This seems not to be the case with a special EXEC_ASSIGN_CALL...
think of B(2:n) = B(1:n-1)
The compiler has to implement this as do i = n, 2, -1 b(i) = b(i-1) end do (or something equivalent, say copying via a temporary) instead of do i = 2, n b(i) = b(i-1) end do
Hope this helps, - Tobi
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |