public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "laurent.chardon at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/65903] New: Line continuation followed by comment character in string fails to compile Date: Mon, 27 Apr 2015 14:16:00 -0000 [thread overview] Message-ID: <bug-65903-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65903 Bug ID: 65903 Summary: Line continuation followed by comment character in string fails to compile Product: gcc Version: 5.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: laurent.chardon at gmail dot com Target Milestone: --- Created attachment 35405 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35405&action=edit Test case that fails when zero or more blank characters separate an & and a ! in a string The fix implemented for https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64506 has introduced a new bug. Now when a string contains the characters "&!" next to each other, the scanner erroneously deletes the rest of the line. The attached test case shows the problem.
next reply other threads:[~2015-04-27 14:16 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-27 14:16 laurent.chardon at gmail dot com [this message] 2015-04-29 1:51 ` [Bug fortran/65903] [5/6 Regression] " jvdelisle at gcc dot gnu.org 2015-05-14 2:05 ` jvdelisle at gcc dot gnu.org 2015-05-14 20:09 ` laurent.chardon at gmail dot com 2015-05-16 17:52 ` jvdelisle at gcc dot gnu.org 2015-05-20 1:51 ` jvdelisle at gcc dot gnu.org 2015-05-20 1:52 ` jvdelisle at gcc dot gnu.org 2015-05-20 1:53 ` 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-65903-4@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).