From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 0D37A386F81B; Sat, 12 Sep 2020 08:20:54 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0D37A386F81B
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1599898854;
 bh=eniSfF8rL9KgbaR2B+vBF3SoepOJoxZWGQQHjsy4IzQ=;
 h=From:To:Subject:Date:From;
 b=UB+5/EdhB2HJcJJfRcr1+nNjkl2LkEmM4Go6nqg0HXcQIe5aSkoDjlS2Rvy2QEQF1
 Xx7wvsNW78QVstOmIJeEhCrtQTYmu1hUdedqKGkrs7i2eGbbap1CJ62U5tuGlheQhU
 lP2QVcJ7VvbON9tR8ZUgW5qTovTdY7JEXEpz+Vso=
From: "jean-pierre.flament@univ-lille.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/97031] New: the content of a comment line breaks
 compilation
Date: Sat, 12 Sep 2020 08:20:53 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.4.7
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jean-pierre.flament@univ-lille.fr
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status
 bug_severity priority component assigned_to reporter target_milestone
 attachments.created
Message-ID: <bug-97031-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Sep 2020 08:20:54 -0000

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D97031

            Bug ID: 97031
           Summary: the content of a comment line breaks compilation
           Product: gcc
           Version: 4.4.7
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jean-pierre.flament@univ-lille.fr
  Target Milestone: ---

Created attachment 49211
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D49211&action=3Dedit
contains  fortran pgm, system and compile info and output

I would like to signal to you a compilation problem that I have solved.

the following comment line

!   some text...  DIR/*/)

seems to put the compiler into trouble. (see attachment)

changing the line to=20

!   some text... DIR/d2)

solves the problem

The attached file contains=20

1) the fortran (self contained)=20=20
    The faulty line is marked =3D=3D> FAULTY LINE,
    it is followed by the line =3D=3D=3D> LINE OK
2) the system name  (centos 6.10) and kernel
3) the command to compile
4) the output

all these parts are sepaated by =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =
 lines

I have also tested gfortran 6.3 (from devtoolset of centos) on the same
computer (As far as I remember the errors are different but the compilation
fails), and gfortran 4.9.3 also on a centos machine: same as 4.4.7).
Sorry I have not access to newer versions of gfortran=