public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/55362] [4.6/4.7/4.8 Regression] ICE with size() on character pointer
Date: Tue, 11 Dec 2012 14:46:00 -0000	[thread overview]
Message-ID: <bug-55362-4-5Vj2qLVGYg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55362-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55362

Tobias Burnus <burnus at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |ice-on-invalid-code
                 CC|                            |burnus at gcc dot gnu.org

--- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-12-11 14:46:03 UTC ---
Untested patch. However, I think we need to do more. I think it won't cover the
DIM= argument and other intrinsics are presumably also affected.


--- a/gcc/fortran/check.c
+++ b/gcc/fortran/check.c
@@ -3593,4 +3593,11 @@ gfc_try
 gfc_check_size (gfc_expr *array, gfc_expr *dim, gfc_expr *kind)
 {
+  if (array->ts.type == BT_PROCEDURE)
+    {
+      gfc_error ("'%s' argument of '%s' intrinsic at %L may not be a
procedure",
+                gfc_current_intrinsic_arg[0]->name, gfc_current_intrinsic,
+                &array->where);
+      return FAILURE;
+    }
   if (array_check (array, 0) == FAILURE)
     return FAILURE;


  parent reply	other threads:[~2012-12-11 14:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-17 10:36 [Bug fortran/55362] New: " dominiq at lps dot ens.fr
2012-11-17 10:39 ` [Bug fortran/55362] " dominiq at lps dot ens.fr
2012-12-11 10:39 ` rguenth at gcc dot gnu.org
2012-12-11 14:46 ` burnus at gcc dot gnu.org [this message]
2013-01-12 16:11 ` pault at gcc dot gnu.org
2013-02-09  9:50 ` pault at gcc dot gnu.org
2013-02-09  9:55 ` [Bug fortran/55362] [4.6/4.7 " pault at gcc dot gnu.org
2013-03-02 17:25 ` mikael at gcc dot gnu.org
2013-03-03 18:09 ` paul.richard.thomas at gmail dot com
2013-03-10 18:35 ` pault at gcc dot gnu.org
2013-03-10 20:15 ` pault at gcc dot gnu.org
2013-03-10 21:03 ` pault at gcc dot gnu.org
2013-03-11  6:20 ` izamyatin at gmail dot com
2013-03-11  8:31 ` burnus at gcc dot gnu.org
2013-03-11 17:43 ` dominiq at lps dot ens.fr

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=bug-55362-4-5Vj2qLVGYg@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).