public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/39811] New: Bogus warning for valid continuation lines Date: Sat, 18 Apr 2009 22:19:00 -0000 [thread overview] Message-ID: <bug-39811-13404@http.gcc.gnu.org/bugzilla/> (raw) Found in http://groups.google.com/group/comp.lang.fortran/browse_thread/thread/58d772090de9d1f4 Test case by Dick Hendrickson, gfortran tested by Ron Shepard. The executable is OK, but gfortran prints a bogus warning: Warning: '&' not allowed by itself in line 2 (The run-time result is: Print rather a lot of ampersands &&&&&&&&&&& ) PRINT *, 'Print rather a lot of ampersands &&&&& &&&&& &&&&&' end -- Summary: Bogus warning for valid continuation lines Product: gcc Version: 4.5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: burnus at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39811
next reply other threads:[~2009-04-18 22:19 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-04-18 22:19 burnus at gcc dot gnu dot org [this message] 2009-04-18 22:32 ` [Bug fortran/39811] " burnus at gcc dot gnu dot org 2009-04-20 21:48 ` burnus at gcc dot gnu dot org 2009-04-20 22:19 ` burnus at gcc dot gnu dot org 2009-04-20 22:21 ` burnus at gcc dot gnu dot 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-39811-13404@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).