public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/19425] Duplicate SAVE attribute problem
Date: Mon, 24 Oct 2005 15:09:00 -0000	[thread overview]
Message-ID: <20051024150944.2346.qmail@sourceware.org> (raw)
In-Reply-To: <bug-19425-7575@http.gcc.gnu.org/bugzilla/>



------- Comment #8 from pinskia at gcc dot gnu dot org  2005-10-24 15:09 -------
Fixed for 4.1 by:
        fortran/
        * decl.c (gfc_match_save): Changed duplicate SAVE errors to
        warnings in the absence of strict standard conformance
        * symbol.c (gfc_add_save): Same.


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED
   Target Milestone|---                         |4.1.0


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


       reply	other threads:[~2005-10-24 15:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-19425-7575@http.gcc.gnu.org/bugzilla/>
2005-10-24 15:09 ` pinskia at gcc dot gnu dot org [this message]
2005-01-13 14:26 [Bug fortran/19425] New: " tow21 at cam dot ac dot uk
2005-01-13 14:59 ` [Bug fortran/19425] " tow21 at cam dot ac dot uk
2005-01-14 23:41 ` pinskia at gcc dot gnu dot org
2005-02-13 14:59 ` pinskia at gcc dot gnu dot org
2005-03-22 18:36 ` kargl at gcc dot gnu dot org
2005-05-06 13:08 ` Konrad dot Bernloehr at mpi-hd dot mpg dot de
2005-05-06 13:22 ` tow21 at cam dot ac dot uk
2005-05-07 15:56 ` tobi at gcc dot gnu dot org
2005-09-18  5:36 ` pinskia 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=20051024150944.2346.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).