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/51605] internal compiler error gfc_trans_block_construct, at fortran/trans-stmt.c:984
Date: Mon, 19 Dec 2011 11:52:00 -0000	[thread overview]
Message-ID: <bug-51605-4-afHe0INzOY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51605-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-12-19 11:39:55 UTC ---
Created attachment 26139
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26139
Draft patch (for the rejects-valid part, not for the ICE)

Draft patch, which allows again
  ptr => associate-name
It also fixes an ICE ("class_ok" part, "(a)") and issues with coarrays and
select type. [Coarrays now fail after resolution with an ICE.]

Test cases (a) to (d):

type t
end type t
class(t), target :: p1               ! (a) Invalid (was ICEing before)
!class(t), allocatable, target :: p1 ! (b) Valid (unchanged by the patch)
!class(t), allocatable :: p1         ! (c) Correctly fails (ditto)
!class(t), pointer :: p1             ! (d) Valid (now accepted)
class(t), pointer :: p2

select type(p1)
  type is(t)
    p2 => p1
  class is(t)
    p2 => p1
end select
end

 * * *

Having fixed the rejects-valid issue, one again hits:
  internal compiler error: in gfc_trans_block_construct, at
fortran/trans-stmt.c:1215

1209      ns = code->ext.block.ns;
1211      sym = ns->proc_name;
1215      gcc_assert (!sym->tlink);

Here, "sym->name" is "eval_int_expr" and sym->tlink == sym.


The issue is seemingly the following code in an internal procedure:
      integer_or_logical: select type(symbol_ptr)
      ...
      end select integer_or_logical

and then another internal procedure:

  subroutine integer_or_logical( expr_str, flag)
    ...
  end subroutine integer_or_logical

  recursive subroutine eval_int_expr( int_expr, value)

The label "integer_or_logical" of the block some clashes with the same-named
subroutine - and thus marks the subroutine which follows somehow as
EXPR_BLOCK?!?


  parent reply	other threads:[~2011-12-19 11:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-17 22:46 [Bug fortran/51605] New: " danlnagle at me dot com
2011-12-17 23:26 ` [Bug fortran/51605] " danlnagle at me dot com
2011-12-17 23:48 ` dominiq at lps dot ens.fr
2011-12-18  9:24 ` kargl at gcc dot gnu.org
2011-12-18 10:08 ` burnus at gcc dot gnu.org
2011-12-18 13:55 ` danlnagle at me dot com
2011-12-18 14:15 ` burnus at gcc dot gnu.org
2011-12-18 16:57 ` sgk at troutmask dot apl.washington.edu
2011-12-19 11:52 ` burnus at gcc dot gnu.org [this message]
2011-12-19 13:19 ` burnus at gcc dot gnu.org
2011-12-19 15:32 ` burnus at gcc dot gnu.org
2011-12-19 15:54 ` danlnagle at me dot com
2011-12-19 18:56 ` burnus at gcc dot gnu.org
2011-12-19 20:26 ` burnus at gcc dot gnu.org
2011-12-19 20:30 ` burnus at gcc dot gnu.org
2013-12-14 20:15 ` dominiq at lps dot ens.fr
2013-12-14 22:25 ` janus at gcc dot gnu.org
2023-03-06 17:18 ` anlauf 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-51605-4-afHe0INzOY@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).