public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/64506] FORMAT Parse Error with Continuation Line Date: Fri, 13 Feb 2015 16:58:00 -0000 [thread overview] Message-ID: <bug-64506-4-eb8s8us7YX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64506-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64506 --- Comment #3 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> --- Author: jvdelisle Date: Fri Feb 13 16:57:28 2015 New Revision: 220687 URL: https://gcc.gnu.org/viewcvs?rev=220687&root=gcc&view=rev Log: 2015-02-13 Jerry DeLisle <jvdelisle@gcc.gnu.org> PR fortran/64506 * scanner.c (gfc_next_char_literal): For free form source, check for '!' and if found, clear the comment and go back and get the next character. For fixed form source, skip the rest of the line. Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/scanner.c
next prev parent reply other threads:[~2015-02-13 16:58 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-06 5:59 [Bug fortran/64506] New: " thfanning at gmail dot com 2015-01-09 10:30 ` [Bug fortran/64506] " dominiq at lps dot ens.fr 2015-02-01 20:42 ` burnus at gcc dot gnu.org 2015-02-13 16:58 ` jvdelisle at gcc dot gnu.org [this message] 2015-02-13 17:09 ` jvdelisle at gcc dot gnu.org 2015-02-17 20:13 ` jvdelisle at gcc dot gnu.org 2015-03-01 2:29 ` jvdelisle at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-64506-4-eb8s8us7YX@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).