From: Paul Richard Thomas <paul.richard.thomas@gmail.com>
To: Tobias Burnus <burnus@net-b.de>
Cc: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch, fortran] PR58618 - Wrong code with character substring and ASSOCIATE
Date: Thu, 18 Oct 2018 10:10:00 -0000 [thread overview]
Message-ID: <CAGkQGiLKn2aAgo8xkvO=Q-pztfC=FECNYF5dBJ8hy_yO+3Bn_w@mail.gmail.com> (raw)
In-Reply-To: <bcb48ca8-0212-f11e-70d9-2362d7f5b283@net-b.de>
[-- Attachment #1: Type: text/plain, Size: 1980 bytes --]
I do not think that there will be a PR for the ICE. This is a
regression introduced by my patch for PR70149 (September 30th). A
patch is attached. I will commit it as 'obvious' as soon as it has
finished regtesting. I will also commit the patch for PR58618 shortly
afterwards. Thanks for the review.
Paul
On Wed, 17 Oct 2018 at 22:17, Tobias Burnus <burnus@net-b.de> wrote:
>
> Hi Paul,
>
> Paul Richard Thomas wrote:
> > This problem concerned associate targets being substrings. It turns
> > out that they are returned as pointer types (with a different cast for
> > unity based substrings ***sigh***) and so can be assigned directly to
> > the associate name. The patch quite simply removed the condition that
> > such targets be allocatable, pointer or dummy.
> > I noticed in the course of working up the testcase that
> > character (:), pointer :: ptr => NULL()
> > character (6), target :: tgt = 'lmnopq'
> > ptr => tgt
> > print *, len (ptr), ptr
> > end
> > ICEs on the NULL initialization of the pointer but works fine if this
> > is removed. Has this already been posted as a PR?
>
>
> I leave it to Dominique to search for a PR; otherwise, I believe the
> attach patch fixes the issue. – It just needs someone to package it with
> a test case, regtest and commit it.
>
>
> > Bootstrapped and regtested on FC28/x86_64 - OK for trunk?
>
> OK – thanks for the fix.
>
> Tobias
>
> > 2018-10-17 Paul Thomas <pault@gcc.gnu.org>
> >
> > PR fortran/58618
> > * trans-stmt.c (trans_associate_var): All strings that return
> > as pointer types can be assigned directly to the associate
> > name so remove 'attr' and the condition that uses it.
> >
> > 2018-10-17 Paul Thomas <pault@gcc.gnu.org>
> >
> > PR fortran/58618
> > * gfortran.dg/associate_45.f90 : New test.
--
"If you can't explain it simply, you don't understand it well enough"
- Albert Einstein
[-- Attachment #2: ice.diff --]
[-- Type: text/x-patch, Size: 1864 bytes --]
Index: gcc/fortran/trans-decl.c
===================================================================
*** gcc/fortran/trans-decl.c (revision 265231)
--- gcc/fortran/trans-decl.c (working copy)
*************** gfc_get_symbol_decl (gfc_symbol * sym)
*** 1762,1768 ****
gfc_finish_var_decl (length, sym);
if (!sym->attr.associate_var
&& TREE_CODE (length) == VAR_DECL
! && sym->value && sym->value->ts.u.cl->length)
{
gfc_expr *len = sym->value->ts.u.cl->length;
DECL_INITIAL (length) = gfc_conv_initializer (len, &len->ts,
--- 1762,1769 ----
gfc_finish_var_decl (length, sym);
if (!sym->attr.associate_var
&& TREE_CODE (length) == VAR_DECL
! && sym->value && sym->value->expr_type != EXPR_NULL
! && sym->value->ts.u.cl->length)
{
gfc_expr *len = sym->value->ts.u.cl->length;
DECL_INITIAL (length) = gfc_conv_initializer (len, &len->ts,
*************** gfc_get_symbol_decl (gfc_symbol * sym)
*** 1772,1778 ****
DECL_INITIAL (length));
}
else
! gcc_assert (!sym->value);
}
gfc_finish_var_decl (decl, sym);
--- 1773,1779 ----
DECL_INITIAL (length));
}
else
! gcc_assert (!sym->value || sym->value->expr_type == EXPR_NULL);
}
gfc_finish_var_decl (decl, sym);
Index: gcc/testsuite/gfortran.dg/deferred_character_30.f90
===================================================================
*** gcc/testsuite/gfortran.dg/deferred_character_30.f90 (nonexistent)
--- gcc/testsuite/gfortran.dg/deferred_character_30.f90 (working copy)
***************
*** 0 ****
--- 1,9 ----
+ ! { dg-do compile }
+ !
+ ! Fix a regression introduced by the patch for PR70149.
+ !
+ character (:), pointer :: ptr => NULL() ! The NULL () caused an ICE.
+ character (6), target :: tgt = 'lmnopq'
+ ptr => tgt
+ print *, len (ptr), ptr
+ end
next prev parent reply other threads:[~2018-10-18 10:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 10:33 Paul Richard Thomas
2018-10-17 21:17 ` Tobias Burnus
2018-10-18 10:10 ` Paul Richard Thomas [this message]
2018-10-18 10:39 ` Paul Richard Thomas
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='CAGkQGiLKn2aAgo8xkvO=Q-pztfC=FECNYF5dBJ8hy_yO+3Bn_w@mail.gmail.com' \
--to=paul.richard.thomas@gmail.com \
--cc=burnus@net-b.de \
--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).