public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/50549] New: should detect different type parameters in structure constructors (r178939)
@ 2011-09-28  9:10 zeccav at gmail dot com
  2013-06-22 15:20 ` [Bug fortran/50549] " dominiq at lps dot ens.fr
                   ` (5 more replies)
  0 siblings, 6 replies; 7+ messages in thread
From: zeccav at gmail dot com @ 2011-09-28  9:10 UTC (permalink / raw)
  To: gcc-bugs

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

             Bug #: 50549
           Summary: should detect different type parameters in structure
                    constructors (r178939)
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: zeccav@gmail.com


! should detect different type parameters in structure constructors (r178939)
      interface
       function f1()
        character(1),pointer :: f1
       end
      end interface
      type t
       character(2), pointer ::  p2
      end type
      character(1), pointer ::  p1
      type(t) u
      u=t(p1)    ! different character length
      u=t(f1())  ! type parameters are different (Fortran 95 section 4.4.4)
      end


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

end of thread, other threads:[~2022-03-29 18:49 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-09-28  9:10 [Bug fortran/50549] New: should detect different type parameters in structure constructors (r178939) zeccav at gmail dot com
2013-06-22 15:20 ` [Bug fortran/50549] " dominiq at lps dot ens.fr
2021-02-27  8:27 ` zeccav at gmail dot com
2022-03-24 21:13 ` anlauf at gcc dot gnu.org
2022-03-27 19:45 ` anlauf at gcc dot gnu.org
2022-03-29 18:36 ` cvs-commit at gcc dot gnu.org
2022-03-29 18:49 ` anlauf at gcc dot gnu.org

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