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/39229] No warning of truncated lines if a continuation line follows Date: Wed, 18 Feb 2009 10:20:00 -0000 [thread overview] Message-ID: <20090218102031.10550.qmail@sourceware.org> (raw) In-Reply-To: <bug-39229-13648@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from burnus at gcc dot gnu dot org 2009-02-18 10:20 ------- I think that also happens if one does not have a procedure call but simply have a succeeding continuation line, e.g.: print *, min(1,2) [...] some long line & , 2 And it seems to happen also with free-form code which has warning enabled by default. -- burnus at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |burnus at gcc dot gnu dot | |org Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfirmed|0000-00-00 00:00:00 |2009-02-18 10:20:31 date| | Summary|fixed-form: silent line |No warning of truncated |truncation in procedure |lines if a continuation line |calls |follows http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39229
next prev parent reply other threads:[~2009-02-18 10:20 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-02-18 9:46 [Bug fortran/39229] New: fixed-form: silent line truncation in procedure calls dfranke at gcc dot gnu dot org 2009-02-18 10:20 ` burnus at gcc dot gnu dot org [this message] 2009-02-18 16:41 ` [Bug fortran/39229] No warning of truncated lines if a continuation line follows burnus at gcc dot gnu dot org 2009-02-23 19:38 ` dfranke at gcc dot gnu dot org 2009-03-08 18:05 ` jvdelisle at gcc dot gnu dot org 2009-07-25 16:46 ` jvdelisle at gcc dot gnu dot org 2009-07-25 17:10 ` burnus at gcc dot gnu dot org 2009-09-01 3:02 ` jvdelisle at gcc dot gnu dot org 2009-09-02 1:04 ` jvdelisle at gcc dot gnu dot org 2009-09-02 1:19 ` jvdelisle 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=20090218102031.10550.qmail@sourceware.org \ --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).