From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: FX <fxcoudert@gmail.com>
Cc: fortran@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] PR fortran/67987 -- character lengths cannot be negative
Date: Fri, 16 Oct 2015 21:39:00 -0000 [thread overview]
Message-ID: <20151016212657.GA22421@troutmask.apl.washington.edu> (raw)
In-Reply-To: <E0AD3803-1E0A-410F-BA35-FA8B367716F5@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]
On Fri, Oct 16, 2015 at 10:17:34PM +0200, FX wrote:
> > The attach patch enforces the Fortran Standard's requirement
> > that character length must be great than or equal to zero.
>
> 4.4.3.2. "If the character length parameter value evaluates to
> a negative value, the length of character entities declared is zero."
>
Thanks. I missed the above. The above text goes back to
at least F90 (see p. 41 on N693.pdf). New diff attached.
2015-10-16 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/67987
* decl.c (char_len_param_value): Unwrap unlong line. If LEN < 0,
then force it to zero pre Fortran Standards.
* resolve.c (gfc_resolve_substring_charlen): Unwrap unlong line.
If 'start' is larger than 'end', then length of string is negative,
so explicitly set it to zero.
(resolve_charlen): Remove -Wsurprising warning. Update comment to
text from F2008 standard.
2015-10-16 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/67987
* gfortran.dg/char_length_2.f90: Add declaration from PR to testcase.
--
Steve
[-- Attachment #2: pr67987.diff --]
[-- Type: text/x-diff, Size: 5173 bytes --]
Index: fortran/decl.c
===================================================================
--- fortran/decl.c (revision 228667)
+++ fortran/decl.c (working copy)
@@ -697,8 +697,7 @@ char_len_param_value (gfc_expr **expr, b
if (gfc_match_char (':') == MATCH_YES)
{
- if (!gfc_notify_std (GFC_STD_F2003, "deferred type "
- "parameter at %C"))
+ if (!gfc_notify_std (GFC_STD_F2003, "deferred type parameter at %C"))
return MATCH_ERROR;
*deferred = true;
@@ -708,11 +707,13 @@ char_len_param_value (gfc_expr **expr, b
m = gfc_match_expr (expr);
- if (m == MATCH_YES
- && !gfc_expr_check_typed (*expr, gfc_current_ns, false))
+ if (m == MATCH_NO || m == MATCH_ERROR)
+ return m;
+
+ if (!gfc_expr_check_typed (*expr, gfc_current_ns, false))
return MATCH_ERROR;
- if (m == MATCH_YES && (*expr)->expr_type == EXPR_FUNCTION)
+ if ((*expr)->expr_type == EXPR_FUNCTION)
{
if ((*expr)->value.function.actual
&& (*expr)->value.function.actual->expr->symtree)
@@ -731,6 +732,15 @@ char_len_param_value (gfc_expr **expr, b
}
}
}
+
+ /* F2008, 4.4.3.1: The length is a type parameter; its kind is processor
+ dependent and its value is greater than or equal to zero.
+ F2008, 4.4.3.2: If the character length parameter value evaluates to
+ a negative value, the length of character entities declared is zero. */
+ if ((*expr)->expr_type == EXPR_CONSTANT
+ && mpz_cmp_si ((*expr)->value.integer, 0) < 0)
+ mpz_set_si ((*expr)->value.integer, 0);
+
return m;
syntax:
Index: fortran/resolve.c
===================================================================
--- fortran/resolve.c (revision 228667)
+++ fortran/resolve.c (working copy)
@@ -4562,8 +4562,7 @@ gfc_resolve_substring_charlen (gfc_expr
{
if (e->ts.u.cl->length)
gfc_free_expr (e->ts.u.cl->length);
- else if (e->expr_type == EXPR_VARIABLE
- && e->symtree->n.sym->attr.dummy)
+ else if (e->expr_type == EXPR_VARIABLE && e->symtree->n.sym->attr.dummy)
return;
}
@@ -4596,12 +4595,19 @@ gfc_resolve_substring_charlen (gfc_expr
return;
}
- /* Length = (end - start +1). */
+ /* Length = (end - start + 1). */
e->ts.u.cl->length = gfc_subtract (end, start);
e->ts.u.cl->length = gfc_add (e->ts.u.cl->length,
gfc_get_int_expr (gfc_default_integer_kind,
NULL, 1));
+ /* F2008, 6.4.1: Both the starting point and the ending point shall
+ be within the range 1, 2, ..., n unless the starting point exceeds
+ the ending point, in which case the substring has length zero. */
+
+ if (mpz_cmp_si (e->ts.u.cl->length->value.integer, 0) < 0)
+ mpz_set_si (e->ts.u.cl->length->value.integer, 0);
+
e->ts.u.cl->length->ts.type = BT_INTEGER;
e->ts.u.cl->length->ts.kind = gfc_charlen_int_kind;
@@ -10882,18 +10888,11 @@ resolve_charlen (gfc_charlen *cl)
}
}
- /* "If the character length parameter value evaluates to a negative
- value, the length of character entities declared is zero." */
+ /* F2008, 4.4.3.2: If the character length parameter value evaluates to
+ a negative value, the length of character entities declared is zero. */
if (cl->length && !gfc_extract_int (cl->length, &i) && i < 0)
- {
- if (warn_surprising)
- gfc_warning_now (OPT_Wsurprising,
- "CHARACTER variable at %L has negative length %d,"
- " the length has been set to zero",
- &cl->length->where, i);
- gfc_replace_expr (cl->length,
+ gfc_replace_expr (cl->length,
gfc_get_int_expr (gfc_default_integer_kind, NULL, 0));
- }
/* Check that the character length is not too large. */
k = gfc_validate_kind (BT_INTEGER, gfc_charlen_int_kind, false);
Index: testsuite/gfortran.dg/char_length_2.f90
===================================================================
--- testsuite/gfortran.dg/char_length_2.f90 (revision 228667)
+++ testsuite/gfortran.dg/char_length_2.f90 (working copy)
@@ -1,22 +1,13 @@
-! { dg-do link }
-! { dg-options "-Wsurprising" }
-! Tests the fix for PR 31250
-! CHARACTER lengths weren't reduced early enough for all checks of
-! them to be meaningful. Furthermore negative string lengths weren't
-! dealt with correctly.
-CHARACTER(len=0) :: c1 ! This is OK.
-CHARACTER(len=-1) :: c2 ! { dg-warning "has negative length" }
+! { dg-do compile }
+! Original test came in with fix for PR 31250.
+! The last line tests the fix for PR fortran/67987.
+!
PARAMETER(I=-100)
-CHARACTER(len=I) :: c3 ! { dg-warning "has negative length" }
-CHARACTER(len=min(I,500)) :: c4 ! { dg-warning "has negative length" }
-CHARACTER(len=max(I,500)) :: d1 ! no warning
-CHARACTER(len=5) :: d2 ! no warning
-
-if (len(c1) .ne. 0) call link_error ()
-if (len(c2) .ne. len(c1)) call link_error ()
-if (len(c3) .ne. len(c2)) call link_error ()
-if (len(c4) .ne. len(c3)) call link_error ()
-
-if (len(d1) .ne. 500) call link_error ()
-if (len(d2) .ne. 5) call link_error ()
+CHARACTER(len=0) :: c1
+CHARACTER(len=-1) :: c2
+CHARACTER(len=I) :: c3
+CHARACTER(len=min(I,500)) :: c4
+CHARACTER(len=max(I,500)) :: d1
+CHARACTER(len=5) :: d2
+character(-8) :: c = ' '
END
next prev parent reply other threads:[~2015-10-16 21:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 19:31 Steve Kargl
2015-10-16 20:21 ` FX
2015-10-16 21:39 ` Steve Kargl [this message]
2015-10-16 21:41 ` FX
2015-10-16 22:38 ` Steve Kargl
2015-10-17 0:07 ` Steve Kargl
2015-10-17 9:27 ` FX
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=20151016212657.GA22421@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--cc=fortran@gcc.gnu.org \
--cc=fxcoudert@gmail.com \
--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).