[Bug fortran/30407] Elemental functions in WHERE assignments wrongly rejected

2007-01-27 Thread pault at gcc dot gnu dot org
--- Comment #6 from pault at gcc dot gnu dot org 2007-01-27 18:23 --- Subject: Bug 30407 Author: pault Date: Sat Jan 27 18:23:14 2007 New Revision: 121235 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=121235 Log: 2007-01-27 Paul Thomas [EMAIL PROTECTED] PR

[Bug fortran/30407] Elemental functions in WHERE assignments wrongly rejected

2007-01-21 Thread patchapp at dberlin dot org
--- Comment #4 from patchapp at dberlin dot org 2007-01-21 22:00 --- Subject: Bug number PR30407 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-01/msg01744.html --

[Bug fortran/30407] Elemental functions in WHERE assignments wrongly rejected

2007-01-21 Thread pault at gcc dot gnu dot org
--- Comment #5 from pault at gcc dot gnu dot org 2007-01-22 05:17 --- Dang it! In spite of New Year's resolutions, I had better take it. Paul -- pault at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/30407] Elemental functions in WHERE assignments wrongly rejected

2007-01-17 Thread pault at gcc dot gnu dot org
--- Comment #3 from pault at gcc dot gnu dot org 2007-01-17 14:11 --- Expected: As elemental procedures are also allowed, a case EXEC_ASSIGN_CALL: has to be added. This is the easy bit... You then get: $ /irun/bin/gfortran pr30407.f90 pr30407.f90: In function 'MAIN__':

[Bug fortran/30407] Elemental functions in WHERE assignments wrongly rejected

2007-01-09 Thread pault at gcc dot gnu dot org
--- Comment #2 from pault at gcc dot gnu dot org 2007-01-09 20:36 --- (In reply to comment #1) A look into resolve.c's resolve_where, shows that only EXEC_ASSIGN and not EXEC_ASSIGN_CALL exists in switch (cnext-op). Expected: As elemental procedures are also allowed, a case