public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Mikael Morin <mikael@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-8229] fortran: Generate an array temporary reference [PR102043]
Date: Fri, 22 Apr 2022 20:53:35 +0000 (GMT)	[thread overview]
Message-ID: <20220422205335.9E11D3856DFC@sourceware.org> (raw)

https://gcc.gnu.org/g:761dda57482295f9c41fcf87e5defa2ac1959f03

commit r12-8229-g761dda57482295f9c41fcf87e5defa2ac1959f03
Author: Mikael Morin <mikael@gcc.gnu.org>
Date:   Fri Apr 22 22:52:38 2022 +0200

    fortran: Generate an array temporary reference [PR102043]
    
    This avoids regressing on char_cast_1.f90 and char_cast_2.f90 later in
    the patch series when the code generation for array references is
    changed to use pointer arithmetic.
    
    The regressing testcases match part of an array reference in the
    generated tree dump and it’s not clear how the pattern should be
    rewritten to match the equivalent with pointer arithmetic.
    
    This change uses a method specific to array temporaries to generate
    array-references, so that these array references are flagged as safe
    for array indexing and will not be updated to use pointer arithmetic.
    
            PR fortran/102043
    
    gcc/fortran/ChangeLog:
            * trans-array.cc (gfc_conv_expr_descriptor): Use
            gfc_conv_tmp_array_ref.

Diff:
---
 gcc/fortran/trans-array.cc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/fortran/trans-array.cc b/gcc/fortran/trans-array.cc
index b3f8871ff22..11e47c0c1ca 100644
--- a/gcc/fortran/trans-array.cc
+++ b/gcc/fortran/trans-array.cc
@@ -7723,7 +7723,7 @@ gfc_conv_expr_descriptor (gfc_se *se, gfc_expr *expr)
       lse.ss = loop.temp_ss;
       rse.ss = ss;
 
-      gfc_conv_scalarized_array_ref (&lse, NULL);
+      gfc_conv_tmp_array_ref (&lse);
       if (expr->ts.type == BT_CHARACTER)
 	{
 	  gfc_conv_expr (&rse, expr);


                 reply	other threads:[~2022-04-22 20:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220422205335.9E11D3856DFC@sourceware.org \
    --to=mikael@gcc.gnu.org \
    --cc=gcc-cvs@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).