public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steve dot chapel at a2pg dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/38404]  New: Warning message identifies incorrect line
Date: Thu, 04 Dec 2008 17:04:00 -0000	[thread overview]
Message-ID: <bug-38404-14861@http.gcc.gnu.org/bugzilla/> (raw)

When the following program (truncbug.f) is compiled with gfortran 4.3.2:

      SUBROUTINE ERRMSG(N,STRING,LST)
      CHARACTER*72 TEXT(2)
      DATA (TEXT(I),I=1,2)/
     X'MUST BE "CALL SIMEPS(EPS)"',
     X'"R" IN CALL RANDOM MAY NOT BE USED OUTSIDE THE BLOCK CONTAINING T
     XHE CALL.'/
      END

This warning message results:

truncbug.f:4.72:

     X'MUST BE "CALL SIMEPS(EPS)"',                                     
                                                                       1
Warning: initialization string truncated to match variable at (1)

This is two lines before the line that the string truncation occurs on.
Ideally, gfortran should put the (1) mark at the character in the string where
the truncation occurs.


-- 
           Summary: Warning message identifies incorrect line
           Product: gcc
           Version: 4.3.2
            Status: UNCONFIRMED
          Severity: minor
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: steve dot chapel at a2pg dot com
 GCC build triplet: i386-redhat-linux
  GCC host triplet: i386-redhat-linux
GCC target triplet: i386-redhat-linux


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38404


             reply	other threads:[~2008-12-04 17:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-04 17:04 steve dot chapel at a2pg dot com [this message]
2009-03-28 12:20 ` [Bug fortran/38404] " fxcoudert at gcc dot gnu dot org
2010-05-13 12:30 ` dfranke at gcc dot gnu dot org
2010-05-13 13:15 ` steve dot chapel at a2pg dot com
2010-05-13 13:26 ` dfranke at gcc dot gnu dot org
2010-05-13 16:28 ` steve dot chapel at a2pg dot com
2010-05-19 12:55 ` dfranke at gcc dot gnu dot org
2010-05-19 12:57 ` dfranke 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-38404-14861@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).