From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: fortran@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: [PATCH] Fortran cleanup patch
Date: Thu, 10 May 2018 23:08:00 -0000 [thread overview]
Message-ID: <20180510230817.GA43099@troutmask.apl.washington.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 223 bytes --]
The attached patch removed an unused function.
OK to commit?
2018-05-10 Steven G. Kargl <kargl@gcc.gnu.org>
* gfortran.h: Remove prototype.
* symbol.c (gfc_new_undo_checkpoint): Remove unused function.
--
Steve
[-- Attachment #2: unused.diff --]
[-- Type: text/x-diff, Size: 1449 bytes --]
Index: gcc/fortran/gfortran.h
===================================================================
--- gcc/fortran/gfortran.h (revision 260141)
+++ gcc/fortran/gfortran.h (working copy)
@@ -3033,7 +3033,6 @@ int gfc_get_sym_tree (const char *, gfc_namespace *, g
int gfc_get_ha_symbol (const char *, gfc_symbol **);
int gfc_get_ha_sym_tree (const char *, gfc_symtree **);
-void gfc_new_undo_checkpoint (gfc_undo_change_set &);
void gfc_drop_last_undo_checkpoint (void);
void gfc_restore_last_undo_checkpoint (void);
void gfc_undo_symbols (void);
Index: gcc/fortran/symbol.c
===================================================================
--- gcc/fortran/symbol.c (revision 260141)
+++ gcc/fortran/symbol.c (working copy)
@@ -3484,22 +3484,6 @@ find_common_symtree (gfc_symtree *st, gfc_common_head
}
-/* Clear the given storage, and make it the current change set for registering
- changed symbols. Its contents are freed after a call to
- gfc_restore_last_undo_checkpoint or gfc_drop_last_undo_checkpoint, but
- it is up to the caller to free the storage itself. It is usually a local
- variable, so there is nothing to do anyway. */
-
-void
-gfc_new_undo_checkpoint (gfc_undo_change_set &chg_syms)
-{
- chg_syms.syms = vNULL;
- chg_syms.tbps = vNULL;
- chg_syms.previous = latest_undo_chgset;
- latest_undo_chgset = &chg_syms;
-}
-
-
/* Restore previous state of symbol. Just copy simple stuff. */
static void
next reply other threads:[~2018-05-10 23:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 23:08 Steve Kargl [this message]
2018-05-13 12:32 ` Andre Vehreschild
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=20180510230817.GA43099@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@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).