public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "domob at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/29835] Error message of unknown edit descriptor needs improvement
Date: Tue, 22 Jul 2008 17:07:00 -0000	[thread overview]
Message-ID: <20080722170640.11611.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29835-13404@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from domob at gcc dot gnu dot org  2008-07-22 17:06 -------
Subject: Bug 29835

Author: domob
Date: Tue Jul 22 17:05:55 2008
New Revision: 138063

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=138063
Log:
2008-07-22  Daniel Kraft  <d@domob.eu>

        PR fortran/29835
        * io.c (error_element), (format_locus):  New static globals.
        (unexpected_element):  Spelled out this message fully.
        (next_char):  Keep track of locus when not MODE_STRING.
        (next_char_not_space):  Remember last parsed element in error_element.
        (format_lex):  Fix two indentation errors.
        (check_format):  Use format_locus and possibly error_element for a
        slightly better error message on invalid format.
        (check_format_string):  Set format_locus to start of the string
        expression used as format.

2008-07-22  Daniel Kraft  <d@domob.eu>

        PR fortran/29835
        * io/format.c (struct format_data):  New member error_element.
        (unexpected_element):  Added '%c' to message.
        (next_char):  Keep track of last parsed character in
fmt->error_element.
        (format_error):  If the message is unexpected_element, output the
        offending character, too.

2008-07-22  Daniel Kraft  <d@domob.eu>

        PR fortran/29835
        * gfortran.dg/fmt_error_3.f90:  New test.
        * gfortran.dg/fmt_error_4.f90:  New test.
        * gfortran.dg/fmt_error_5.f90:  New test.


Added:
    trunk/gcc/testsuite/gfortran.dg/fmt_error_3.f90
    trunk/gcc/testsuite/gfortran.dg/fmt_error_4.f90
    trunk/gcc/testsuite/gfortran.dg/fmt_error_5.f90
Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/io.c
    trunk/gcc/testsuite/ChangeLog
    trunk/libgfortran/ChangeLog
    trunk/libgfortran/io/format.c


-- 


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


  parent reply	other threads:[~2008-07-22 17:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-14 18:01 [Bug fortran/29835] New: Error message of non-unknown " burnus at gcc dot gnu dot org
2006-11-14 18:01 ` [Bug fortran/29835] " burnus at gcc dot gnu dot org
2007-01-02  4:51 ` [Bug fortran/29835] Error message of unknown " jvdelisle at gcc dot gnu dot org
2007-09-08 20:16 ` jvdelisle at gcc dot gnu dot org
2008-07-22 17:07 ` domob at gcc dot gnu dot org [this message]
2008-07-22 17:11 ` domob 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=20080722170640.11611.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: 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).