--- Comment #7 from dh458 at oakapple dot net 2009-10-08 13:23 ---
Subject: Re: mixing common and modules elicits seg fault
> The use of common in the context of this PR badly hurts my understanding of
commons: storage arrays computed at compile time.
For better or worse, the Sun Stud
--- Comment #6 from dominiq at lps dot ens dot fr 2009-10-08 08:43 ---
The use of common in the context of this PR badly hurts my understanding of
commons: storage arrays computed at compile time. The standard says (f2008):
5.7.2 COMMON statement
5.7.2.1 General
1 The COMMON statement
--- Comment #5 from burnus at gcc dot gnu dot org 2009-10-08 07:47 ---
Backtrace (of comment 3) using an older GCC 4.5 (20090526):
#0 0x00549453 in gfc_trans_pointer_assignment (expr1=0x12d8ea0,
expr2=0x12d3b80)
at /home/tob/projects/gcc-trunk-checkout/gcc/fortran/trans-expr
--- Comment #4 from dh458 at oakapple dot net 2009-10-08 00:19 ---
Subject: Re: mixing common and modules elicits seg fault
>
Note that if I comment the line " common/arrays/Ro" I get the following link
error:
Undefined symbols:
"_span.0", referenced from:
_span.0$non_lazy_
--- Comment #3 from dominiq at lps dot ens dot fr 2009-10-07 23:57 ---
Confirmed for gfortran 4.3.4, 4.4.1, and trunk. The code compiles with gfortran
4.2.4, thus this is a regression. Reduced test:
module testmod
integer, parameter :: r8 = selected_real_kind(12)
type VARIABLES_MA
--- Comment #2 from kargl at gcc dot gnu dot org 2009-10-07 23:21 ---
Here's a reduced testcase.
module testmod
type variables_maille
real, dimension(5) :: cell_var
end type variables_maille
type(variables_maille), pointer, dimension(:,:,:) :: hydro_vars
common /arrays
--- Comment #1 from dh458 at oakapple dot net 2009-10-07 22:54 ---
Created an attachment (id=18747)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18747&action=view)
example file tor segmentation violation with gfortran 4.4.1
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41627
