Re: [Patch, Fortran] -fcoarray=lib - add registering calls for nonallocatable coarrays

2011-05-26 Thread Paul Richard Thomas
> However, I forgot the [*]  (or [3,*] or ...). Fortunately, you > have spotted the sematically relevant typo! > ;-) Paul

Re: [Patch, Fortran] -fcoarray=lib - add registering calls for nonallocatable coarrays

2011-05-26 Thread Tobias Burnus
Dear Paul, thanks for the review. Regarding: Paul Thomas wrote: > Maybe I am being stupid but what is the call, in the > testcase, to subroutine test for? Well, it is supposed to test coarray decls in functions, contained functions, and in not-referenced functions. However, I forgot the [*] (

Re: [Patch, Fortran] -fcoarray=lib - add registering calls for nonallocatable coarrays

2011-05-26 Thread Paul Richard Thomas
Dear Tobias, This looks fine to me. It does the things that you described and is well hidden behind the co-array associated conditions. Thus it is OK for trunk. Maybe I am being stupid but what is the call, in the testcase, to subroutine test for? Cheers Paul

Re: [Patch, Fortran] -fcoarray=lib - add registering calls for nonallocatable coarrays

2011-05-25 Thread Tobias Burnus
ping**0.3 http://gcc.gnu.org/ml/fortran/2011-05/msg00176.html Tobias Burnus wrote: Instead of a ping, an updated patch. This one additionally supports registering of nonallocatable coarrays also in MODULE and in BLOCK plus a test case. (Changes to gfc_generate_module_vars and gfc_process_blo

Re: [Patch, Fortran] -fcoarray=lib - add registering calls for nonallocatable coarrays

2011-05-24 Thread Tobias Burnus
Instead of a ping, an updated patch. This one additionally supports registering of nonallocatable coarrays also in MODULE and in BLOCK plus a test case. (Changes to gfc_generate_module_vars and gfc_process_block_locals and cgraph call in generate_coarray_init; some functions were moved up in

[Patch, Fortran] -fcoarray=lib - add registering calls for nonallocatable coarrays

2011-05-22 Thread Tobias Burnus
The following applies to -fcoarray=lib; for -fcoarray=single there should be no change. The coarray communication library needs to know about the coarrays even before the function containing them has been invoked. Thus, the coarrays (of all translation units) need to be registered at start up.