public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/46705] Spurious "Missing '&' in continued character constant" warning occurs twice
Date: Sat, 11 Dec 2010 23:15:00 -0000	[thread overview]
Message-ID: <bug-46705-4-c9hg1ABi65@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46705-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> 2010-12-11 23:14:48 UTC ---
Author: jvdelisle
Date: Sat Dec 11 23:14:45 2010
New Revision: 167716

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=167716
Log:
2010-12-11  Jerry DeLisle  <jvdelisle@gcc.gnu.org>

    PR fortran/46705
    * gfortran.h: New enum gfc_instring.
    (gfc_next_char_literal): Update prototype.
    * scanner.c (gfc_next_char_literal): Use new enum. Only give missing
    '&' warning for INSTRING_WARN. (gfc_next_char): Use new enum.
    (gfc_gobble_whitespace): Likewise.
    * io.c (next_char): Use new enum. (next_char_not_space): Likewise.
    (format_lex): Likewise.
    * match.c (gfc_match_parens): Likewise.
    (gfc_match_special_char): Likewise. (gfc_match_name_C): Likewise.
    * parse.c (next_fixed): Likewise.
    * primary.c (match_hollerith_constant): Likewise.
    (next_string_char): Likewise.

Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/gfortran.h
    trunk/gcc/fortran/io.c
    trunk/gcc/fortran/match.c
    trunk/gcc/fortran/parse.c
    trunk/gcc/fortran/primary.c
    trunk/gcc/fortran/scanner.c


  parent reply	other threads:[~2010-12-11 23:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-29 10:56 [Bug fortran/46705] New: " mathewc at nag dot co.uk
2010-11-29 21:02 ` [Bug fortran/46705] " burnus at gcc dot gnu.org
2010-12-08  4:41 ` jvdelisle at gcc dot gnu.org
2010-12-11 15:55 ` jvdelisle at gcc dot gnu.org
2010-12-11 16:02 ` jvdelisle at gcc dot gnu.org
2010-12-11 20:42 ` jvdelisle at gcc dot gnu.org
2010-12-11 23:15 ` jvdelisle at gcc dot gnu.org [this message]
2010-12-11 23:26 ` jvdelisle at gcc dot gnu.org
2010-12-11 23:34 ` 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-46705-4-c9hg1ABi65@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).