- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
we are trying to use some f77 code inside a f90 code.
We put all common blocks in one module and use this module were needed.
This works with most of other compilers but not with Compaq's. The problems seems to come from the presence of the blank common block. Here is an example code and the compilation error...
and the compilation ends with this
we are trying to use some f77 code inside a f90 code.
We put all common blocks in one module and use this module were needed.
This works with most of other compilers but not with Compaq's. The problems seems to come from the presence of the blank common block. Here is an example code and the compilation error...
module commons
implicit integer(n)
common // nwork
end module commons
module test_mod
use commons
implicit none
integer :: a=1
end module test_mod
program test
use test_mod
implicit none
nwork=0
print *,nwork,a
end program test
and the compilation ends with this
f90 test.f90
f90: Severe: test.f90, line 4: **Internal compiler error: segmentation violation
signal raised** Please report this error along with the circumstances in which
it occurred in a Software Problem Report. Note: File and line given may not be
explicit cause of this error.
end module commons
^
Link Copied
5 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You're using a very old compiler version. try a newer one. This works fine in 5.4.
Steve
Steve
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Not realy. This error I get with these versions...
> f90 -version
Compaq Fortran X5.4A-1684
Compaq Fortran Compiler X5.4A-1684-46B5P
>uname -sprv
OSF1 V5.1 732 alpha
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sorry - I misread the version.
This seems to be something we broke after 5.4. We'll take a look.
Steve
This seems to be something we broke after 5.4. We'll take a look.
Steve
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Have you got any fix/explanation for this problem?
Jaroslav
Jaroslav
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Explanation: it's a compiler bug. Fix - it's too late to fix it in 5.5, but we'll fix it for any update after that.
The easiest workaround is to give the COMMON a name.
Steve
The easiest workaround is to give the COMMON a name.
Steve

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page