fortran-common-block

If I have a variable called var which is in a common block named myCB may I use the same name to pass an argument between two other subroutines which are not using the common block myCB ? The code is like below. Subroutine SR1(Var) !something here using Var end Subroutine SR1 Subroutine SR2() .... Call SR1(B) .... end Subroutine SR2 Subroutine SR3() common \myCB\ Var ... ! something using the other Var shared with SR4 ...... end Subroutine SR3 Subroutine SR4() common \myCB\ Var .... ... ! something using the other Var shared with SR3 .... end Subroutine SR4 I do have problem with Var passing

I develop one C++ program which calls a Fortran 77 routine. The main C++ program may run multithreaded. However, it happens that the Fortran 77 routine hides several common blocks which are modified on each call depending on its arguments. I am afraid that all common blocks may be shared between multiple threads and that concurrent accesses to these blocks will probably mess everything. First question : Am I right? Would common blocks be shared between multiple threads? Second question : Is there a simple way to avoid it? Rewriting the Fortran routines seems unaffordable, I am rather looking

I have a few questions about using common blocks in parallel programming in Fortran. My subroutines have common blocks. Do I have to declare all the common blocks and threadprivate in the parallel do region? How do they pass information? I want seperate common clock for each thread and want them to pass information through the end of parallel region. Does it happen here? My Ford subroutine changes some variables in common blocks and Condact subroutine overwrites over them again but the function uses the values from Condact subroutine. Do the second subroutine and function copy the variables

I'm dealing with some legacy code that uses COMMON blocks extensively and sometimes uses the SAVE statement. After consulting the Fortran standard, it says: The appearance of a common block name preceded and followed by a slash in a SAVE statement has the effect of specifying all of the entities in that common block. Under what circumstances does placing a variable in a common block not imply SAVE ? Since the variable must be accessible in any other program unit that includes that common block, how could it not be SAVE ed? I had to look it up, because I was under the same impression as you are