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] [5/6 Regression] Line continuation followed by comment character in string fails to compile
Date: Thu, 14 May 2015 20:09:00 -0000	[thread overview]
Message-ID: <bug-65903-4-mtgr0suLKy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65903-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Laurent Chardon <laurent.chardon at gmail dot com> ---
Thanks for the fix. If I may suggest a modification of the testcase in order to
check also when there are no blanks between the & and !. I know in Fortran it
shouldn't matter, but I don't see any harm in making sure... 

! { dg-do run }
! { dg-options "-std=gnu" }
! 
character(20) :: astring

100 format ("& notblank !")
200 format ("&          !")
300 format ("&!")

write(astring,100)
if (astring.ne."& notblank !") call abort
!print *, astring
write(astring,200)
if (astring.ne."&          !") call abort
!print *, astring
write(astring,300)
if (astring.ne."&!") call abort
!print *, astring

end


  parent reply	other threads:[~2015-05-14 20:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-27 14:16 [Bug fortran/65903] New: " laurent.chardon at gmail dot com
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 [this message]
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-mtgr0suLKy@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: link
Be 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).