[Bug fortran/41714] [OOP] ALLOCATE SOURCE= does not properly copy the value from SOURCE

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

[Bug fortran/41714] [OOP] ALLOCATE SOURCE= does not properly copy the value from SOURCE

2009-10-26 Thread janus at gcc dot gnu dot org
--- Comment #8 from janus at gcc dot gnu dot org 2009-10-26 09:08 --- Subject: Bug 41714 Author: janus Date: Mon Oct 26 09:08:03 2009 New Revision: 153547 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=153547 Log: 2009-10-26 Janus Weil ja...@gcc.gnu.org PR

[Bug fortran/41714] [OOP] ALLOCATE SOURCE= does not properly copy the value from SOURCE

2009-10-26 Thread janus at gcc dot gnu dot org
--- Comment #9 from janus at gcc dot gnu dot org 2009-10-26 09:13 --- Fixed with r153547. Closing. -- janus at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/41714] [OOP] ALLOCATE SOURCE= does not properly copy the value from SOURCE

2009-10-25 Thread janus at gcc dot gnu dot org
--- Comment #5 from janus at gcc dot gnu dot org 2009-10-25 10:24 --- (In reply to comment #4) internal compiler error: in tree_annotate_all_with_location, at gimplify.c:892 This goes away with the following patchlet: Index: gcc/fortran/trans-expr.c

[Bug fortran/41714] [OOP] ALLOCATE SOURCE= does not properly copy the value from SOURCE

2009-10-25 Thread dominiq at lps dot ens dot fr
--- Comment #6 from dominiq at lps dot ens dot fr 2009-10-25 13:55 --- The patches in comment #1 and #5 seem to work as advertized (currently regtesting). After having looked at the f2003 standard draft, I understand that allocate(a, source=t2(1,2)) is equivalent to allocate(t2::a)

[Bug fortran/41714] [OOP] ALLOCATE SOURCE= does not properly copy the value from SOURCE

2009-10-25 Thread dominiq at lps dot ens dot fr
--- Comment #7 from dominiq at lps dot ens dot fr 2009-10-25 17:20 --- (In reply to comment #6) Did I missed something in the standard or is this a bug? Probably the former!-(If I move a%j=2 inside the type is (t2) block, the code compiles without error). --

[Bug fortran/41714] [OOP] ALLOCATE SOURCE= does not properly copy the value from SOURCE

2009-10-16 Thread janus at gcc dot gnu dot org
--- Comment #4 from janus at gcc dot gnu dot org 2009-10-16 21:25 --- (In reply to comment #3) In addition to this there are two more test cases failing: Sorry, these were fake (my local source tree was messed up). The only real failure is class_allocate_1.f03, from which one can

[Bug fortran/41714] [OOP] ALLOCATE SOURCE= does not properly copy the value from SOURCE

2009-10-16 Thread janus at gcc dot gnu dot org
--- Comment #3 from janus at gcc dot gnu dot org 2009-10-16 16:22 --- (In reply to comment #2) Problem: The patch in comment #1 regresses on class_allocate_1.f03: In addition to this there are two more test cases failing: Native configuration is x86_64-unknown-linux-gnu

[Bug fortran/41714] [OOP] ALLOCATE SOURCE= does not properly copy the value from SOURCE

2009-10-15 Thread janus at gcc dot gnu dot org
--- Comment #1 from janus at gcc dot gnu dot org 2009-10-15 13:14 --- Certainly mine. I should have thought of this case when fixing PR41581. The cure is for sure: Index: gcc/fortran/trans-stmt.c === ---

[Bug fortran/41714] [OOP] ALLOCATE SOURCE= does not properly copy the value from SOURCE

2009-10-15 Thread janus at gcc dot gnu dot org
--- Comment #2 from janus at gcc dot gnu dot org 2009-10-15 20:27 --- Problem: The patch in comment #1 regresses on class_allocate_1.f03: gfortran-4.5 class_allocate_1.f03 -O1 class_allocate_1.f03: In function ‘MAIN__’: class_allocate_1.f03:57:0: internal compiler error: in