https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43895
janus at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |4.6.0
--- Comment #12 from pault at gcc dot gnu dot org 2010-06-05 10:40 ---
(In reply to comment #11)
OK, all this has a simple explanation. A revamped version of the original
testcase segfaults in runtime, at -O0.
! { dg-do compile }
! Test the fix for PR43895, in which the dummy 'a' was
--- Comment #13 from pault at gcc dot gnu dot org 2010-06-05 14:08 ---
(In reply to comment #12)
This is tiresome - it regtested fine, I update the tree and now I get failures
on:
alloc_comp_result_1.f90
alloc_comp_scalar_1.f90
alloc_comp_transformational_1.f90
All three segfault at
--- Comment #14 from pault at gcc dot gnu dot org 2010-06-05 17:51 ---
Subject: Bug 43895
Author: pault
Date: Sat Jun 5 17:51:39 2010
New Revision: 160326
URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=160326
Log:
2010-06-05 Paul Thomas pa...@gcc.gnu.org
PR
--- Comment #15 from janus at gcc dot gnu dot org 2010-06-06 03:17 ---
I guess we can close this, right?
--
janus at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #9 from sfilippone at uniroma2 dot it 2010-05-18 10:41 ---
(In reply to comment #8)
(In reply to comment #7)
Btw, after the recent patch for PR43969, this might well be fixed already ...
Unfortunately, no, I still get the ICE.
--
--- Comment #10 from janus at gcc dot gnu dot org 2010-05-18 12:19 ---
(In reply to comment #9)
Btw, after the recent patch for PR43969, this might well be fixed already
...
Unfortunately, no, I still get the ICE.
Sure. Actually my comment was only targeted towards Tobias'
--- Comment #11 from burnus at gcc dot gnu dot org 2010-05-18 12:24 ---
(In reply to comment #8)
If one adds b = ALLOCATED(x) one finds:
Where do you add this?
Add in bug14 of attachment 20491 before 'end subroutine':
logical b
b = allocated(a%a)
However, this is now fixed.
*
--- Comment #7 from burnus at gcc dot gnu dot org 2010-05-17 20:22 ---
Propagate comment from PR 43990:
There seems to be an inconsistency with CLASS with POINTER
or ALLOCATABLE attribute: Is class.$DATA or class the pointer variable. If
one adds b = ALLOCATED(x) one finds:
--- Comment #8 from janus at gcc dot gnu dot org 2010-05-17 20:35 ---
(In reply to comment #7)
If one adds b = ALLOCATED(x) one finds:
Where do you add this? I don't see a test case where this fits into. Can you
give a complete example?
Btw, after the recent patch for PR43969, this
--- Comment #6 from burnus at gcc dot gnu dot org 2010-05-06 16:28 ---
See also PR 43990 - I think the PRs might be related, though I have not really
studied this PR.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43895
--- Comment #4 from janus at gcc dot gnu dot org 2010-04-26 15:04 ---
Confirmed.
It seems this fails already with the 4.5 release as well as with current trunk,
which means that it's not specific to the fortran-dev branch.
--
janus at gcc dot gnu dot org changed:
What
--- Comment #5 from sfilippone at uniroma2 dot it 2010-04-26 15:32 ---
(In reply to comment #0)
The attached code produces the subject message, but only with optimization; at
-O0 it works.
-- behaviour --
[sfili...@localhost bug14]$ gfortran -O1 -c bug14.f90
13 matches
Mail list logo
