[Bug fortran/45451] [OOP] Inconsistent status of ALLOCATABLE components inside CLASS variables.

2016-11-16 Thread janus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=45451 janus at gcc dot gnu.org changed: What|Removed |Added Target Milestone|--- |4.6.0

[Bug fortran/45451] [OOP] Inconsistent status of ALLOCATABLE components inside CLASS variables.

2010-11-05 Thread janus at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45451 --- Comment #17 from janus at gcc dot gnu.org 2010-11-05 18:15:02 UTC --- Author: janus Date: Fri Nov 5 18:14:52 2010 New Revision: 166368 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=166368 Log: 2010-11-05 Janus Weil ja...@gcc.gnu.org

[Bug fortran/45451] [OOP] Inconsistent status of ALLOCATABLE components inside CLASS variables.

2010-11-05 Thread janus at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45451 janus at gcc dot gnu.org changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

[Bug fortran/45451] [OOP] Inconsistent status of ALLOCATABLE components inside CLASS variables.

2010-10-26 Thread burnus at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45451 --- Comment #15 from Tobias Burnus burnus at gcc dot gnu.org 2010-10-26 06:49:47 UTC --- Author: burnus Date: Tue Oct 26 06:49:43 2010 New Revision: 165936 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=165936 Log: 2010-10-26 Tobias Burnus

[Bug fortran/45451] [OOP] Inconsistent status of ALLOCATABLE components inside CLASS variables.

2010-10-26 Thread burnus at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45451 Tobias Burnus burnus at gcc dot gnu.org changed: What|Removed |Added Depends on||46174 ---

[Bug fortran/45451] [OOP] Inconsistent status of ALLOCATABLE components inside CLASS variables.

2010-10-24 Thread burnus at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45451 Tobias Burnus burnus at gcc dot gnu.org changed: What|Removed |Added CC||burnus at gcc

[Bug fortran/45451] [OOP] Inconsistent status of ALLOCATABLE components inside CLASS variables.

2010-10-24 Thread burnus at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45451 --- Comment #13 from Tobias Burnus burnus at gcc dot gnu.org 2010-10-24 21:42:33 UTC --- (In reply to comment #12) If one looks at the dump Scratch that part. In one case one allocates the component (integr(4)*4) in the other case the type,

[Bug fortran/45451] [OOP] Inconsistent status of ALLOCATABLE components inside CLASS variables.

2010-10-24 Thread burnus at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45451 --- Comment #14 from Tobias Burnus burnus at gcc dot gnu.org 2010-10-24 22:31:19 UTC --- (In reply to comment #13) The following works - though I am not sure whether it is the correct patch. Janus, what do you think? I mean in particular

[Bug fortran/45451] [OOP] Inconsistent status of ALLOCATABLE components inside CLASS variables.

2010-10-05 Thread sfilippone at uniroma2 dot it
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45451 --- Comment #11 from Salvatore Filippone sfilippone at uniroma2 dot it 2010-10-05 19:39:44 UTC --- (In reply to comment #4) Ok, I could reduce this quite a bit: 1 3 4 5 1 3

[Bug fortran/45451] [OOP] Inconsistent status of ALLOCATABLE components inside CLASS variables.

2010-09-01 Thread burnus at gcc dot gnu dot org
--- Comment #10 from burnus at gcc dot gnu dot org 2010-09-01 12:02 --- I think this is a variant of PR 42647: Allocatable components of allocatable scalars are not correctly handled. -- burnus at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/45451] [OOP] Inconsistent status of ALLOCATABLE components inside CLASS variables.

2010-08-31 Thread sfilippone at uniroma2 dot it
--- Comment #5 from sfilippone at uniroma2 dot it 2010-08-31 14:04 --- (In reply to comment #4) Ok, I could reduce this quite a bit: Good :) In the meantime, I tried with MOLD= in place of SOURCE=, and in the full application it still gives a segfault; I think that variant should be

[Bug fortran/45451] [OOP] Inconsistent status of ALLOCATABLE components inside CLASS variables.

2010-08-31 Thread janus at gcc dot gnu dot org
--- Comment #6 from janus at gcc dot gnu dot org 2010-08-31 14:17 --- (In reply to comment #5) In the meantime, I tried with MOLD= in place of SOURCE=, and in the full application it still gives a segfault; I think that variant should be checked as well. Note that for MOLD there is

[Bug fortran/45451] [OOP] Inconsistent status of ALLOCATABLE components inside CLASS variables.

2010-08-31 Thread sfilippone at uniroma2 dot it
--- Comment #7 from sfilippone at uniroma2 dot it 2010-08-31 14:18 --- (In reply to comment #6) Note that for MOLD there is PR 44541 left (which I am about to fix). Up to now MOLD works only with non-polymorphic expressions. Once the PR is fixed, polymorphics should work too. Until

[Bug fortran/45451] [OOP] Inconsistent status of ALLOCATABLE components inside CLASS variables.

2010-08-31 Thread sfilippone at uniroma2 dot it
--- Comment #8 from sfilippone at uniroma2 dot it 2010-08-31 19:20 --- (In reply to comment #7) (In reply to comment #6) Fine. Waiting for it Consider the following variation: upon exit from DOIT, the ACSR variable should be deallocated (since it was MOVE_ALLOCed to atx%a)

[Bug fortran/45451] [OOP] Inconsistent status of ALLOCATABLE components inside CLASS variables.

2010-08-31 Thread sfilippone at uniroma2 dot it
--- Comment #9 from sfilippone at uniroma2 dot it 2010-08-31 19:21 --- Created an attachment (id=21613) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21613action=view) test case -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45451

[Bug fortran/45451] [OOP] Inconsistent status of ALLOCATABLE components inside CLASS variables.

2010-08-30 Thread sfilippone at uniroma2 dot it
--- Comment #1 from sfilippone at uniroma2 dot it 2010-08-30 12:09 --- Created an attachment (id=21592) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21592action=view) test case -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45451

[Bug fortran/45451] [OOP] Inconsistent status of ALLOCATABLE components inside CLASS variables.

2010-08-30 Thread sfilippone at uniroma2 dot it
--- Comment #2 from sfilippone at uniroma2 dot it 2010-08-30 12:12 --- (In reply to comment #0) Hello, After a lot (a LOT) of work, I've come up with this test case. The test case *appears* to run fine, but valgrind shows something is amiss, and in the full application (much more

[Bug fortran/45451] [OOP] Inconsistent status of ALLOCATABLE components inside CLASS variables.

2010-08-30 Thread sfilippone at uniroma2 dot it
--- Comment #3 from sfilippone at uniroma2 dot it 2010-08-30 12:13 --- And here is the (expected) output with XLF. [snfi...@josquin ~]$ xlf2003_r -o bug23 bug23.f03 ** psb_const_mod === End of Compilation 1 === ** psb_base_mat_mod === End of Compilation 2 === ** psb_d_base_mat_mod

[Bug fortran/45451] [OOP] Inconsistent status of ALLOCATABLE components inside CLASS variables.

2010-08-30 Thread janus at gcc dot gnu dot org
-- janus at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1

[Bug fortran/45451] [OOP] Inconsistent status of ALLOCATABLE components inside CLASS variables.

2010-08-30 Thread janus at gcc dot gnu dot org
--- Comment #4 from janus at gcc dot gnu dot org 2010-08-30 20:48 --- Ok, I could reduce this quite a bit: program bug23 implicit none type :: psb_base_sparse_mat integer, allocatable :: irp(:) end type psb_base_sparse_mat class(psb_base_sparse_mat), allocatable :: a