public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/59781] [4.7/4.8/4.9 Regression] [F03] Incorrect initialisation of derived type
Date: Mon, 13 Jan 2014 08:38:00 -0000	[thread overview]
Message-ID: <bug-59781-4-uDX7bMmqWa@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59781-4@http.gcc.gnu.org/bugzilla/>

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

janus at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |4.9.0
            Summary|[4.9 Regression] [F03]      |[4.7/4.8/4.9 Regression]
                   |Incorrect initialisation of |[F03] Incorrect
                   |derived type                |initialisation of derived
                   |                            |type

--- Comment #3 from janus at gcc dot gnu.org ---
I verified that the problem is not specific to ISO_C_BINDING and occurs also
when replacing type(c_ptr) by some other derived type.

The following variant works with 4.4 (printing '1' as expected), but fails with
4.6 and above (printing some random number):


  implicit none

  type t1
    integer :: s
  end type

  type t2
    type(t1) :: state = t1(1)
    real, allocatable :: store(:)
  end type

  call test

contains

  subroutine test
    type(t2) :: rng
    print *,rng%state%s
  end subroutine

end


  parent reply	other threads:[~2014-01-13  8:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-12 21:26 [Bug fortran/59781] New: " james.s.spencer at gmail dot com
2014-01-12 21:41 ` [Bug fortran/59781] [4.9 Regression] [F03] " janus at gcc dot gnu.org
2014-01-12 21:56 ` janus at gcc dot gnu.org
2014-01-13  8:38 ` janus at gcc dot gnu.org [this message]
2014-01-13  8:56 ` [Bug fortran/59781] [4.7/4.8/4.9 " dominiq at lps dot ens.fr
2014-01-13  9:18 ` jakub at gcc dot gnu.org
2014-01-13 15:49 ` janus at gcc dot gnu.org
2014-01-13 19:58 ` janus at gcc dot gnu.org
2014-04-22 11:38 ` [Bug fortran/59781] [4.7/4.8/4.9/4.10 " jakub at gcc dot gnu.org
2014-07-16 13:30 ` [Bug fortran/59781] [4.8/4.9/4.10 " jakub at gcc dot gnu.org
2014-10-30 10:42 ` [Bug fortran/59781] [4.8/4.9/5 " jakub at gcc dot gnu.org
2015-06-26 19:56 ` [Bug fortran/59781] [4.9/5/6 " jakub at gcc dot gnu.org
2015-06-26 20:28 ` jakub 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-59781-4-uDX7bMmqWa@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).