public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/51993] Erroneous type component initialization leads to internal compiler error
Date: Thu, 29 Oct 2015 12:34:00 -0000	[thread overview]
Message-ID: <bug-51993-4-MUglNZqjTR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51993-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51993

--- Comment #5 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> Changing the gcc_assert to an early return gives ...

Confirmed with the patch

--- ../_clean/gcc/fortran/decl.c        2015-10-27 18:14:22.000000000 +0100
+++ gcc/fortran/decl.c  2015-10-29 12:02:02.000000000 +0100
@@ -1293,7 +1293,9 @@ gfc_set_constant_character_len (int len,
   int slen;

   gcc_assert (expr->expr_type == EXPR_CONSTANT);
-  gcc_assert (expr->ts.type == BT_CHARACTER);
+  /* gcc_assert (expr->ts.type == BT_CHARACTER); */
+  if (expr->ts.type != BT_CHARACTER)
+    return;

   slen = expr->value.character.length;
   if (len != slen)

No regression.


  parent reply	other threads:[~2015-10-29 12:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-25 10:28 [Bug fortran/51993] New: " bardeau at iram dot fr
2012-01-25 11:14 ` [Bug fortran/51993] " burnus at gcc dot gnu.org
2013-02-27 15:56 ` dominiq at lps dot ens.fr
2015-10-29 10:54 ` dominiq at lps dot ens.fr
2015-10-29 12:34 ` dominiq at lps dot ens.fr [this message]
2015-10-30 17:55 ` kargl at gcc dot gnu.org
2015-10-30 18:14 ` kargl at gcc dot gnu.org
2015-10-30 18:27 ` kargl at gcc dot gnu.org
2015-10-30 18:35 ` kargl at gcc dot gnu.org
2015-10-30 18:36 ` kargl at gcc dot gnu.org

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-51993-4-MUglNZqjTR@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).