public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tobias Burnus <tobias@codesourcery.com>
To: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>,
	<gcc-patches@gcc.gnu.org>, <fortran@gcc.gnu.org>
Cc: Bernhard Reutner-Fischer <aldot@gcc.gnu.org>
Subject: Re: [PATCH,Fortran 6/7] Fortran: Delete unused decl in trans-types.h
Date: Tue, 26 Oct 2021 11:40:59 +0200	[thread overview]
Message-ID: <3b54ce75-4182-d1ef-367e-0eb3c5cd5dda@codesourcery.com> (raw)
In-Reply-To: <20211024223023.1410274-7-rep.dot.nop@gmail.com>

On 25.10.21 00:30, Bernhard Reutner-Fischer via Fortran wrote:
> From: Bernhard Reutner-Fischer <aldot@gcc.gnu.org>
> gcc/fortran/ChangeLog:
>
>       * trans-types.h (gfc_convert_function_code): Delete.

OK.

Tobias

> ---
>   gcc/fortran/trans-types.h | 3 ---
>   1 file changed, 3 deletions(-)
>
> diff --git a/gcc/fortran/trans-types.h b/gcc/fortran/trans-types.h
> index 1b43503092b..3bc236cad0d 100644
> --- a/gcc/fortran/trans-types.h
> +++ b/gcc/fortran/trans-types.h
> @@ -65,9 +65,6 @@ enum gfc_packed {
>     PACKED_STATIC
>   };
>
> -/* be-function.c */
> -void gfc_convert_function_code (gfc_namespace *);
> -
>   /* trans-types.c */
>   void gfc_init_kinds (void);
>   void gfc_init_types (void);
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955

  reply	other threads:[~2021-10-26  9:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-24 22:30 [PATCH,Fortran 0/7] delete some unused decls, make static Bernhard Reutner-Fischer
2021-10-24 22:30 ` [PATCH,Fortran 1/7] Fortran: make some trans* functions static Bernhard Reutner-Fischer
2021-10-25  5:47   ` Thomas Koenig
2021-10-25  6:43     ` Tobias Burnus
2021-10-25  8:00       ` Bernhard Reutner-Fischer
2021-10-26  9:34   ` Tobias Burnus
2021-10-24 22:30 ` [PATCH,Fortran 2/7] Fortran: make some match* " Bernhard Reutner-Fischer
2021-10-26  9:37   ` Tobias Burnus
2021-10-24 22:30 ` [PATCH,Fortran 3/7] Fortran: make some constructor* " Bernhard Reutner-Fischer
2021-10-26  9:30   ` Tobias Burnus
2021-10-24 22:30 ` [PATCH,Fortran 4/7] Fortran: make some trans-array " Bernhard Reutner-Fischer
2021-10-26  9:39   ` Tobias Burnus
2021-10-24 22:30 ` [PATCH,Fortran 5/7] Fortran: Delete unused decl in trans-stmt.h Bernhard Reutner-Fischer
2021-10-26  9:40   ` Tobias Burnus
2021-10-24 22:30 ` [PATCH,Fortran 6/7] Fortran: Delete unused decl in trans-types.h Bernhard Reutner-Fischer
2021-10-26  9:40   ` Tobias Burnus [this message]
2021-10-24 22:30 ` [PATCH,Fortran 7/7] Fortran: Delete unused decl in intrinsic.h Bernhard Reutner-Fischer
2021-10-24 22:46 ` [PATCH,Fortran 0/7] delete some unused decls, make static Bernhard Reutner-Fischer
2021-10-25  9:25 ` Bernhard Reutner-Fischer

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=3b54ce75-4182-d1ef-367e-0eb3c5cd5dda@codesourcery.com \
    --to=tobias@codesourcery.com \
    --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).