[Bug fortran/30793] Segfault on calling a function returning a pointer

2007-02-23 Thread burnus at gcc dot gnu dot org
--- Comment #16 from burnus at gcc dot gnu dot org 2007-02-23 20:53 --- Fixed in 4.2 and the trunk. Allocatable components are not in 4.1 and thus this bug fix cannot be ported to 4.1. -- burnus at gcc dot gnu dot org changed: What|Removed |Added -

[Bug fortran/30793] Segfault on calling a function returning a pointer

2007-02-16 Thread burnus at gcc dot gnu dot org
--- Comment #14 from burnus at gcc dot gnu dot org 2007-02-16 09:55 --- Subject: Bug 30793 Author: burnus Date: Fri Feb 16 09:55:20 2007 New Revision: 122037 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=122037 Log: fortran/ 2007-02-16 Tobias Burnus <[EMAIL PROTECTED]>

[Bug fortran/30793] Segfault on calling a function returning a pointer

2007-02-16 Thread sfilippone at uniroma2 dot it
--- Comment #13 from sfilippone at uniroma2 dot it 2007-02-16 09:40 --- (In reply to comment #3) > For both test cases, xlf gives: > > ** class_mesh === End of Compilation 1 === > ** class_field === End of Compilation 2 === > . > (second test case). I don't know if they are rig

[Bug fortran/30793] Segfault on calling a function returning a pointer

2007-02-15 Thread burnus at gcc dot gnu dot org
-- burnus at gcc dot gnu dot org changed: What|Removed |Added AssignedTo|unassigned at gcc dot gnu |burnus at gcc dot gnu dot |dot org

[Bug fortran/30793] Segfault on calling a function returning a pointer

2007-02-15 Thread patchapp at dberlin dot org
--- Comment #12 from patchapp at dberlin dot org 2007-02-15 17:25 --- Subject: Bug number PR30793 A patch for this bug has been added to the patch tracker. The mailing list url for the patch is http://gcc.gnu.org/ml/gcc-patches/2007-02/msg01366.html -- http://gcc.gnu.org/bugzilla/s

[Bug fortran/30793] Segfault on calling a function returning a pointer

2007-02-15 Thread sfilippone at uniroma2 dot it
--- Comment #11 from sfilippone at uniroma2 dot it 2007-02-15 10:42 --- (In reply to comment #10) > > > I have still to re-read the test case to check whether TARGET is required > > > > However the accessed component is a POINTER to a derived type [...] > > Ok, I somehow didn't realiz

[Bug fortran/30793] Segfault on calling a function returning a pointer

2007-02-15 Thread burnus at gcc dot gnu dot org
--- Comment #10 from burnus at gcc dot gnu dot org 2007-02-15 10:32 --- > > I have still to re-read the test case to check whether TARGET is required > > However the accessed component is a POINTER to a derived type [...] Ok, I somehow didn't realize type field type(mesh),

[Bug fortran/30793] Segfault on calling a function returning a pointer

2007-02-15 Thread sfilippone at uniroma2 dot it
--- Comment #9 from sfilippone at uniroma2 dot it 2007-02-15 09:55 --- (In reply to comment #8) > The link to c.l.fortran is: > http://groups.google.com/group/comp.lang.fortran/browse_thread/thread/23aa68ecce460e50 > > Richard Main: "The pointer assignment is ok. I [...] don't have > ti

[Bug fortran/30793] Segfault on calling a function returning a pointer

2007-02-15 Thread burnus at gcc dot gnu dot org
--- Comment #8 from burnus at gcc dot gnu dot org 2007-02-15 09:45 --- The link to c.l.fortran is: http://groups.google.com/group/comp.lang.fortran/browse_thread/thread/23aa68ecce460e50 Richard Main: "The pointer assignment is ok. I [...] don't have time to adequately peruse the rest of

[Bug fortran/30793] Segfault on calling a function returning a pointer

2007-02-14 Thread dominiq at lps dot ens dot fr
--- Comment #7 from dominiq at lps dot ens dot fr 2007-02-14 21:54 --- The following changes --- pr30793.f90 Wed Feb 14 19:50:03 2007 +++ pr30793_red.f90 Wed Feb 14 22:50:04 2007 @@ -33,7 +33,7 @@ end type field interface msh_ -module procedure msh_ +module procedure

[Bug fortran/30793] Segfault on calling a function returning a pointer

2007-02-14 Thread sfilippone at uniroma2 dot it
--- Comment #6 from sfilippone at uniroma2 dot it 2007-02-14 21:18 --- (In reply to comment #5) > ... > My understanding of f90 and above is not sufficient to say if the test cases > are valid or not. > From what I ahve read in different list ifort seems very tolerant, at lea

[Bug fortran/30793] Segfault on calling a function returning a pointer

2007-02-14 Thread dominiq at lps dot ens dot fr
--- Comment #5 from dominiq at lps dot ens dot fr 2007-02-14 21:00 --- On AMD64, gfortran x86_64-unknown-linux-gnu, 4.3.0 20061231, gives: pr30793_1.f90:44.24: use class_scalar_field 1 Error: Name 'msh_' at (1) is an ambiguous reference to 'msh_' from module 'c

[Bug fortran/30793] Segfault on calling a function returning a pointer

2007-02-14 Thread sfilippone at uniroma2 dot it
--- Comment #4 from sfilippone at uniroma2 dot it 2007-02-14 20:35 --- I fail to see how xlf's output can be correct on the first error; fld%msh is a POINTER component. ANd get_scalar_field_msh is set. So there must be something else going on. Intel fortran 9.1 digests it without a glit

[Bug fortran/30793] Segfault on calling a function returning a pointer

2007-02-14 Thread dominiq at lps dot ens dot fr
--- Comment #3 from dominiq at lps dot ens dot fr 2007-02-14 19:00 --- For both test cases, xlf gives: ** class_mesh === End of Compilation 1 === ** class_field === End of Compilation 2 === "pr30793.f90", line 127.5: 1515-039 (S) The target in the pointer assignment must have the TA

[Bug fortran/30793] Segfault on calling a function returning a pointer

2007-02-14 Thread sfilippone at uniroma2 dot it
--- Comment #2 from sfilippone at uniroma2 dot it 2007-02-14 18:10 --- Created an attachment (id=13050) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13050&action=view) test case This has been reduced by Tobias Burnus; I am not sure it is the same because of the PRIVATE attributes

[Bug fortran/30793] Segfault on calling a function returning a pointer

2007-02-14 Thread sfilippone at uniroma2 dot it
--- Comment #1 from sfilippone at uniroma2 dot it 2007-02-14 18:09 --- Created an attachment (id=13049) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13049&action=view) Test case Test case -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30793