public inbox for gcc-regression@sourceware.org
help / color / mirror / Atom feed
From: Tobias Burnus <tobias@codesourcery.com>
To: Jan Hubicka <hubicka@kam.mff.cuni.cz>,
Tobias Burnus <tobias@codesourcery.com>
Cc: sunil.k.pandey <skpandey@sc.intel.com>,
fortran <fortran@gcc.gnu.org>, <gcc-patches@gcc.gnu.org>,
<gcc-regression@gcc.gnu.org>
Subject: [Patch, committed] Fortran: Fix 'fn spec' for deferred character length (was: Re: [r12-4457 Regression] FAIL: gfortran.dg/deferred_type_param_6.f90 -Os execution test on Linux/x86_64)
Date: Tue, 19 Oct 2021 16:49:02 +0200 [thread overview]
Message-ID: <c97b5fd2-616b-f62f-50ff-459ef3f200c2@codesourcery.com> (raw)
In-Reply-To: <20211016185437.GB23986@kam.mff.cuni.cz>
[-- Attachment #1: Type: text/plain, Size: 1675 bytes --]
On 16.10.21 20:54, Jan Hubicka wrote:
> I wrote:
>> Fortran has for a long time 'character(len=5), allocatable" or
>> "character(len=*)". In the first case, the "5" can be ignored as both
>> caller and callee know the length. In the second case, the length is
>> determined by the argument, but it cannot be changed.
>>
>> Since a not-that-short while, 'len=:' together with allocatable/pointer
>> is supported.
>>
>> In the latter case, the value can be change when the array
>> association/allocation is changed.
>> ...
>> + if (!sym->ts.u.cl->length
>> + && ((sym->attr.allocatable && sym->attr.target)
>> + || sym->attr.pointer))
>> + spec[spec_len++] = '.';
>> + if (!sym->ts.u.cl->length && sym->attr.allocatable)
>> + spec[spec_len++] = 'w';
>> + else
>> + spec[spec_len++] = 'R';
> Also escaping is quite important bit of information so it would be
> good to figure out if it really can escape rather than playing safe.
The pointer to the string length variable itself does not escape,
only its integer string value:
subroutine foo(x)
character(len=:), pointer :: x
character(len=:), pointer :: y
y => x
has in the dump:
.y = *_x;
y = (character(kind=1)[1:.y] *) *x;
Thus, 'w' can always be used.
Committed as obvious as r12-4511-gff0eec94e87dfb7dc387f120ca5ade2707aecf50
Tobias
-----------------
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
[-- Attachment #2: committed.diff --]
[-- Type: text/x-patch, Size: 1135 bytes --]
commit ff0eec94e87dfb7dc387f120ca5ade2707aecf50
Author: Tobias Burnus <tobias@codesourcery.com>
Date: Tue Oct 19 16:38:56 2021 +0200
Fortran: Fix 'fn spec' for deferred character length
Shows now up with gfortran.dg/deferred_type_param_6.f90 due to more ME
optimizations, causing fails without this commit.
gcc/fortran/ChangeLog:
* trans-types.c (create_fn_spec): For allocatable/pointer
character(len=:), use 'w' not 'R' as fn spec for the length dummy
argument.
---
gcc/fortran/trans-types.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/gcc/fortran/trans-types.c b/gcc/fortran/trans-types.c
index 50fceebc941..42778067dbe 100644
--- a/gcc/fortran/trans-types.c
+++ b/gcc/fortran/trans-types.c
@@ -3014,7 +3014,11 @@ create_fn_spec (gfc_symbol *sym, tree fntype)
}
if (sym->ts.type == BT_CHARACTER)
{
- spec[spec_len++] = 'R';
+ if (!sym->ts.u.cl->length
+ && (sym->attr.allocatable || sym->attr.pointer))
+ spec[spec_len++] = 'w';
+ else
+ spec[spec_len++] = 'R';
spec[spec_len++] = ' ';
}
}
next prev parent reply other threads:[~2021-10-19 14:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-16 16:11 [r12-4457 Regression] FAIL: gfortran.dg/deferred_type_param_6.f90 -Os execution test on Linux/x86_64 sunil.k.pandey
2021-10-16 18:23 ` Jan Hubicka
2021-10-16 18:48 ` [Patch] (was: Re: [r12-4457 Regression] FAIL: gfortran.dg/deferred_type_param_6.f90 -Os execution test on Linux/x86_64) Tobias Burnus
2021-10-16 18:54 ` Jan Hubicka
2021-10-19 14:49 ` Tobias Burnus [this message]
2021-10-18 9:51 ` [r12-4457 Regression] FAIL: gfortran.dg/deferred_type_param_6.f90 -Os execution test on Linux/x86_64 Richard Biener
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=c97b5fd2-616b-f62f-50ff-459ef3f200c2@codesourcery.com \
--to=tobias@codesourcery.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc-regression@gcc.gnu.org \
--cc=hubicka@kam.mff.cuni.cz \
--cc=skpandey@sc.intel.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).