From: Harald Anlauf <anlauf@gmx.de>
To: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>, fortran@gcc.gnu.org
Cc: gcc-patches@gcc.gnu.org, Bernhard Reutner-Fischer <aldot@gcc.gnu.org>
Subject: Re: [PATCH] Fortran: Remove unused declaration
Date: Sat, 12 Nov 2022 22:23:47 +0100 [thread overview]
Message-ID: <933d0150-32fd-84df-6a8a-a19f8c7d6dbc@gmx.de> (raw)
In-Reply-To: <20221112210535.45202-1-aldot@gcc.gnu.org>
Am 12.11.22 um 22:05 schrieb Bernhard Reutner-Fischer via Gcc-patches:
> This function definition was removed years ago, remove it's prototype.
>
> gcc/fortran/ChangeLog:
>
> * gfortran.h (gfc_check_include): Remove declaration.
> ---
> gcc/fortran/gfortran.h | 1 -
> 1 file changed, 1 deletion(-)
> ---
> Regtests cleanly, ok for trunk?
>
> diff --git a/gcc/fortran/gfortran.h b/gcc/fortran/gfortran.h
> index c4deec0d5b8..ce3ad61bb52 100644
> --- a/gcc/fortran/gfortran.h
> +++ b/gcc/fortran/gfortran.h
> @@ -3208,7 +3208,6 @@ int gfc_at_eof (void);
> int gfc_at_bol (void);
> int gfc_at_eol (void);
> void gfc_advance_line (void);
> -int gfc_check_include (void);
> int gfc_define_undef_line (void);
>
> int gfc_wide_is_printable (gfc_char_t);
OK, thanks.
next prev parent reply other threads:[~2022-11-12 21:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-12 21:05 Bernhard Reutner-Fischer
2022-11-12 21:23 ` Harald Anlauf [this message]
2023-01-19 19:39 ` git out-of-order commit (was Re: [PATCH] Fortran: Remove unused declaration) Jason Merrill
2023-01-19 20:20 ` Harald Anlauf
2023-01-20 4:26 ` Bernhard Reutner-Fischer
2023-01-20 17:33 ` Jason Merrill
2023-01-23 10:37 ` Martin Liška
2023-01-20 22:01 ` Carlos O'Donell
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=933d0150-32fd-84df-6a8a-a19f8c7d6dbc@gmx.de \
--to=anlauf@gmx.de \
--cc=aldot@gcc.gnu.org \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=rep.dot.nop@gmail.com \
/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).