[Bug fortran/36403] [4.4 Regression] Some fortran tests using eoshift fail on SH

2008-07-29 Thread domob at gcc dot gnu dot org
--- Comment #7 from domob at gcc dot gnu dot org 2008-07-29 09:17 --- Fixed. -- domob at gcc dot gnu dot org changed: What|Removed |Added Status|ASSIGNED

[Bug fortran/36403] [4.4 Regression] Some fortran tests using eoshift fail on SH

2008-07-29 Thread domob at gcc dot gnu dot org
--- Comment #6 from domob at gcc dot gnu dot org 2008-07-29 09:12 --- Subject: Bug 36403 Author: domob Date: Tue Jul 29 09:11:51 2008 New Revision: 138234 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=138234 Log: 2008-07-29 Daniel Kraft <[EMAIL PROTECTED]> PR fortran

[Bug fortran/36403] [4.4 Regression] Some fortran tests using eoshift fail on SH

2008-07-28 Thread burnus at gcc dot gnu dot org
--- Comment #5 from burnus at gcc dot gnu dot org 2008-07-28 20:04 --- > and it seems as though PACK and RESHAPE would suffer from the same problem as > EOSHIFT does Seems so. I glanced through F2008 CD but I could not find more potential problems. > Is it ok if I try to write one gene

[Bug fortran/36403] [4.4 Regression] Some fortran tests using eoshift fail on SH

2008-07-28 Thread domob at gcc dot gnu dot org
-- domob at gcc dot gnu dot org changed: What|Removed |Added AssignedTo|unassigned at gcc dot gnu |domob at gcc dot gnu dot org |dot org

[Bug fortran/36403] [4.4 Regression] Some fortran tests using eoshift fail on SH

2008-07-28 Thread domob at gcc dot gnu dot org
--- Comment #4 from domob at gcc dot gnu dot org 2008-07-28 18:41 --- Thanks for all the hints, Tobias! I've had a look through the F2003 standard about intrinsics taking optional char arguments, and it seems as though PACK and RESHAPE would suffer from the same problem as EOSHIFT does

[Bug fortran/36403] [4.4 Regression] Some fortran tests using eoshift fail on SH

2008-07-27 Thread burnus at gcc dot gnu dot org
--- Comment #3 from burnus at gcc dot gnu dot org 2008-07-27 13:52 --- > Isn't this maybe a general problem about optional string arguments? > Or is this really a eoshift-specific problem? I'm just thinking about a > general solution for this kind of problem if it isn't. I think this m

[Bug fortran/36403] [4.4 Regression] Some fortran tests using eoshift fail on SH

2008-07-24 Thread domob at gcc dot gnu dot org
--- Comment #2 from domob at gcc dot gnu dot org 2008-07-24 17:03 --- Isn't this maybe a general problem about optional string arguments? Or is this really a eoshift-specific problem? I'm just thinking about a general solution for this kind of problem if it isn't; in that case it would

[Bug fortran/36403] [4.4 Regression] Some fortran tests using eoshift fail on SH

2008-07-18 Thread rguenth at gcc dot gnu dot org
-- rguenth at gcc dot gnu dot org changed: What|Removed |Added Priority|P3 |P4 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36403

[Bug fortran/36403] [4.4 Regression] Some fortran tests using eoshift fail on SH

2008-06-15 Thread fxcoudert at gcc dot gnu dot org
-- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added AssignedTo|fxcoudert at gcc dot gnu dot|unassigned at gcc dot gnu |org

[Bug fortran/36403] [4.4 Regression] Some fortran tests using eoshift fail on SH

2008-06-11 Thread jsm28 at gcc dot gnu dot org
-- jsm28 at gcc dot gnu dot org changed: What|Removed |Added Target Milestone|--- |4.4.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36403

[Bug fortran/36403] [4.4 Regression] Some fortran tests using eoshift fail on SH

2008-06-02 Thread fxcoudert at gcc dot gnu dot org
--- Comment #1 from fxcoudert at gcc dot gnu dot org 2008-06-02 11:29 --- It's a front-end issue: as the BOUNDARY character argument is not present, its length is not appended to the argument list as it should. I guess we need to add a gfc_conv_intrinsic_eoshift function in trans-intrin