public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/51075] New: ICE with deferred-length character pointer component in derived types
@ 2011-11-10 10:35 burnus at gcc dot gnu.org
  2011-11-23 15:17 ` [Bug fortran/51075] " koen.poppe at cs dot kuleuven.be
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: burnus at gcc dot gnu.org @ 2011-11-10 10:35 UTC (permalink / raw)
  To: gcc-bugs

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

             Bug #: 51075
           Summary: ICE with deferred-length character pointer component
                    in derived types
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: burnus@gcc.gnu.org
        Depends on: 45170


The following program gives an ICE, which is maybe not surprising as
deferred-length components are not yet supported.

internal compiler error: in gfc_get_derived_type, at fortran/trans-types.c:2394

Expected:
- Short term: Reject it ("sorry not yet implemented")
- Long term: Support it.


 character(len=42), target, save :: A
 type :: t
   character(len=:), pointer :: P => A
 end type t
 type(T) :: X
end


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2013-09-02 11:26 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-11-10 10:35 [Bug fortran/51075] New: ICE with deferred-length character pointer component in derived types burnus at gcc dot gnu.org
2011-11-23 15:17 ` [Bug fortran/51075] " koen.poppe at cs dot kuleuven.be
2011-12-15 15:19 ` burnus at gcc dot gnu.org
2011-12-15 15:27 ` burnus at gcc dot gnu.org
2012-01-24  8:06 ` burnus at gcc dot gnu.org
2013-09-02 11:26 ` dominiq at lps dot ens.fr

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).