public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mikael Morin <morin-mikael@orange.fr>
To: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>,
	gcc-patches@gcc.gnu.org
Cc: Bernhard Reutner-Fischer <aldot@gcc.gnu.org>,
	gfortran ML <fortran@gcc.gnu.org>
Subject: Re: [PATCH 2/2] Fortran: Add attribute flatten
Date: Mon, 21 Nov 2022 12:24:11 +0100	[thread overview]
Message-ID: <7b9995a0-792a-8931-a2cd-6bf89130d5bd@orange.fr> (raw)
In-Reply-To: <20221110102031.1366016-3-aldot@gcc.gnu.org>

Le 10/11/2022 à 11:20, Bernhard Reutner-Fischer via Fortran a écrit :
> Bootstrapped and regtested cleanly on x86_unknown-linux.
> The document bits will be rewritten for rst.
> Ok for trunk if the prerequisite target_clones patch is approved?
> 
> gcc/fortran/ChangeLog:
> 
> 	* decl.cc (gfc_match_gcc_attributes): Handle flatten.
> 	* f95-lang.cc (gfc_attribute_table): Add flatten.
> 	* gfortran.texi: Document attribute flatten.
> 
> gcc/testsuite/ChangeLog:
> 
> 	* gfortran.dg/attr_flatten-1.f90: New test.
> ---
>   gcc/fortran/decl.cc                          |  8 +++-
>   gcc/fortran/f95-lang.cc                      |  2 +
>   gcc/fortran/gfortran.texi                    |  8 ++++
>   gcc/testsuite/gfortran.dg/attr_flatten-1.f90 | 41 ++++++++++++++++++++
>   4 files changed, 57 insertions(+), 2 deletions(-)
>   create mode 100644 gcc/testsuite/gfortran.dg/attr_flatten-1.f90
> 
> diff --git a/gcc/fortran/decl.cc b/gcc/fortran/decl.cc
> index d312d4812b6..3d210c26eb5 100644
> --- a/gcc/fortran/decl.cc
> +++ b/gcc/fortran/decl.cc
(...)
> @@ -11849,7 +11850,9 @@ gfc_match_gcc_attributes (void)
>   	if (strcmp (name, ext_attr_list[id].name) == 0)
>   	  break;
>   
> -      if (id == EXT_ATTR_LAST)
> +      if (strcmp (name, "flatten") == 0)
> +	known_attr0args = true; /* Handled below.  We do not need a bit.  */

I don't see the point to have all the attributes needing a bit except 
one that doesn't but needs a specific handling.
What does it look like without the 1/2 patch and if one bit is also used 
for flatten, like the other attributes?

> +      else if (id == EXT_ATTR_LAST)
>   	{
>   	  gfc_error ("Unknown attribute in !GCC$ ATTRIBUTES statement at %C");
>   	  return MATCH_ERROR;

> diff --git a/gcc/fortran/gfortran.texi b/gcc/fortran/gfortran.texi
> index 06e4c8c00a1..be650f28b62 100644
> --- a/gcc/fortran/gfortran.texi
> +++ b/gcc/fortran/gfortran.texi
> @@ -3280,6 +3280,14 @@ contains
>   end module mymod
>   @end smallexample
>   
> +@node flatten
> +
> +Procedures annotated with the @code{flatten} attribute have their
> +callees inlined, if possible.
I'm not a native speaker, but I find this sentence confusing.
The words of the gcc manual you are refering to seem more clear: "every 
call inside the function is inlined, if possible".

> +Please refer to
> +@ref{Top,,Common Function Attributes,gcc,Using the GNU Compiler Collection (GCC)}
> +for details about the respective attribute.
> +
>   The attributes are specified using the syntax
>   
>   @code{!GCC$ ATTRIBUTES} @var{attribute-list} @code{::} @var{variable-list}


  reply	other threads:[~2022-11-21 11:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10 10:20 [PATCH 0/2] " Bernhard Reutner-Fischer
2022-11-10 10:20 ` [PATCH 1/2] Fortran: Cleanup struct ext_attr_t Bernhard Reutner-Fischer
2022-11-21 11:08   ` Mikael Morin
2022-11-21 20:34     ` Bernhard Reutner-Fischer
2022-11-22 11:52       ` Mikael Morin
2022-11-10 10:20 ` [PATCH 2/2] Fortran: Add attribute flatten Bernhard Reutner-Fischer
2022-11-21 11:24   ` Mikael Morin [this message]
2022-11-21 20:13     ` 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=7b9995a0-792a-8931-a2cd-6bf89130d5bd@orange.fr \
    --to=morin-mikael@orange.fr \
    --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).