[Bug fortran/20138] fortran (driver?) bug: array bound checking conflicts with preprocessing

2005-04-10 Thread tkoenig at gcc dot gnu dot org
--- Additional Comments From tkoenig at gcc dot gnu dot org 2005-04-10 08:44 --- (In reply to comment #4) > Subject: Bug 20138 Whoops, an erroneous entry in the Changelog here. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20138

[Bug fortran/20138] fortran (driver?) bug: array bound checking conflicts with preprocessing

2005-04-10 Thread cvs-commit at gcc dot gnu dot org
--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-04-10 08:36 --- Subject: Bug 20138 CVSROOT:/cvs/gcc Module name:gcc Changes by: [EMAIL PROTECTED] 2005-04-10 08:35:40 Modified files: libgfortran: ChangeLog libgfortran/io : t

[Bug fortran/20138] fortran (driver?) bug: array bound checking conflicts with preprocessing

2005-02-22 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-22 14:06 --- -C is not valid option at all for bound checking. -fbounds-check is the correct option. *** This bug has been marked as a duplicate of 18452 *** -- What|Removed |Add

[Bug fortran/20138] fortran (driver?) bug: array bound checking conflicts with preprocessing

2005-02-22 Thread anlauf at hep dot tu-darmstadt dot de
--- Additional Comments From anlauf at hep dot tu-darmstadt dot de 2005-02-22 08:54 --- While I'm at it: the option -pipe also has a funny side effect: f951: error: unrecognized command line option "-95" And it produces a file "-95" in the current directory that contains the preprocess

[Bug fortran/20138] fortran (driver?) bug: array bound checking conflicts with preprocessing

2005-02-22 Thread anlauf at hep dot tu-darmstadt dot de
--- Additional Comments From anlauf at hep dot tu-darmstadt dot de 2005-02-22 08:48 --- It looks very much like a driver problem, because the option -std=f95 instead of -C makes it even funnier: cc1: warning: command line option "-std=f95" is valid for F95 but not for C But at least it