[Bug fortran/41872] wrong-code: Issues with allocatable scalars

2010-01-07 Thread burnus at gcc dot gnu dot org
--- Comment #13 from burnus at gcc dot gnu dot org 2010-01-07 08:12 --- Hopefully, all issues are now fixed. Thus: Mark as FIXED. -- burnus at gcc dot gnu dot org changed: What|Removed |Added ---

[Bug fortran/41872] wrong-code: Issues with allocatable scalars

2010-01-07 Thread burnus at gcc dot gnu dot org
--- Comment #12 from burnus at gcc dot gnu dot org 2010-01-07 08:10 --- Subject: Bug 41872 Author: burnus Date: Thu Jan 7 08:09:51 2010 New Revision: 155687 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=155687 Log: 2010-01-07 Tobias Burnus PR fortran/41872

[Bug fortran/41872] wrong-code: Issues with allocatable scalars

2010-01-04 Thread burnus at gcc dot gnu dot org
--- Comment #11 from burnus at gcc dot gnu dot org 2010-01-05 07:19 --- Subject: Bug 41872 Author: burnus Date: Tue Jan 5 07:19:30 2010 New Revision: 155639 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=155639 Log: 2010-01-05 Tobias Burnus PR fortran/41872

[Bug fortran/41872] wrong-code: Issues with allocatable scalars

2010-01-03 Thread burnus at gcc dot gnu dot org
--- Comment #10 from burnus at gcc dot gnu dot org 2010-01-04 07:43 --- Still TO DO: - SAVED local variables are (probably) mishandled - Check whether other things such as allocatable scalar components, (absent/present) optional dummys etc. work. - allocatable-scalar returning functio

[Bug fortran/41872] wrong-code: Issues with allocatable scalars

2010-01-03 Thread burnus at gcc dot gnu dot org
--- Comment #9 from burnus at gcc dot gnu dot org 2010-01-04 07:31 --- Subject: Bug 41872 Author: burnus Date: Mon Jan 4 07:30:49 2010 New Revision: 155606 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=155606 Log: 2009-01-04 Tobias Burnus PR fortran/41872 *

[Bug fortran/41872] wrong-code: Issues with allocatable scalars

2009-12-30 Thread burnus at gcc dot gnu dot org
--- Comment #8 from burnus at gcc dot gnu dot org 2009-12-30 20:50 --- TODO: > - SAVED local variables are (probably) mishandled > - Check whether other things such as allocatable scalar components, > (absent/present) optional dummys etc. work. - allocatable-scalar returning functions as

[Bug fortran/41872] wrong-code: Issues with allocatable scalars

2009-12-29 Thread burnus at gcc dot gnu dot org
--- Comment #7 from burnus at gcc dot gnu dot org 2009-12-30 00:20 --- Created an attachment (id=19421) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19421&action=view) Patch - Nullifies local variables - Fixes double-allocation check in ALLOCATE statement TODO: - INTENT(OUT) var

[Bug fortran/41872] wrong-code: Issues with allocatable scalars

2009-12-14 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2009-12-15 03:02 --- I have started looking at this. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41872

[Bug fortran/41872] wrong-code: Issues with allocatable scalars

2009-11-01 Thread burnus at gcc dot gnu dot org
--- Comment #5 from burnus at gcc dot gnu dot org 2009-11-01 20:46 --- SAVE problem: Simply adding (!sym->attr.save && (... || ...)) to gfc_trans_deferred_vars does not work as one then reaches "unreachable()"; one should check where SAVE is handles for allocatable arrays, which is pres

[Bug fortran/41872] wrong-code: Issues with allocatable scalars

2009-11-01 Thread burnus at gcc dot gnu dot org
--- Comment #4 from burnus at gcc dot gnu dot org 2009-11-01 17:47 --- Subject: Bug 41872 Author: burnus Date: Sun Nov 1 17:46:50 2009 New Revision: 153795 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=153795 Log: 2009-11-01 Tobias Burnus

[Bug fortran/41872] wrong-code: Issues with allocatable scalars

2009-11-01 Thread burnus at gcc dot gnu dot org
--- Comment #3 from burnus at gcc dot gnu dot org 2009-11-01 16:08 --- First patch: http://gcc.gnu.org/ml/fortran/2009-11/msg1.html TODO: * For ALLOCATABLE, OPTIONAL" dummies: If the argument is present but not allocated, "PRESENT()" returns false. As test case add the lines deal