public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "lei at il dot ibm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/17678] New: USE statement incorrectly initializes allocatable array
Date: Sun, 26 Sep 2004 13:58:00 -0000	[thread overview]
Message-ID: <20040926135843.17678.lei@il.ibm.com> (raw)

% gfortran --static test.f90
% a.out
 oops
Abort (core dumped)

% cat test.f90

module foo
  integer, dimension(:), allocatable :: bar
end module

program main
  use foo
  allocate (bar(100))
  call init
end program main

subroutine init
  use foo
  if (.not.allocated(bar)) then
     print *, 'oops'
     call abort
  endif
end subroutine init

=====================================

And here is the dump-tree-original, which clearly shows the problem:

init ()
{
  extern struct array1_int4 bar;

  bar.data = 0B;           <<<<<<<<<<<<<<<<< ALLOCATION IS LOST HERE
  if (bar.data != 0B == 0)
    {
      _gfortran_filename = "test.f90";
      _gfortran_line = 14;
      _gfortran_ioparm.unit = 6;
      _gfortran_ioparm.list_format = 1;
      _gfortran_st_write ();
      _gfortran_transfer_character ("oops", 4);
      _gfortran_st_write_done ();
      _gfortran_abort ();
    }

-- 
           Summary: USE statement incorrectly initializes allocatable array
           Product: gcc
           Version: 4.0.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: lei at il dot ibm dot com
                CC: gcc-bugs at gcc dot gnu dot org


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


             reply	other threads:[~2004-09-26 13:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-26 13:58 lei at il dot ibm dot com [this message]
2004-09-26 14:15 ` [Bug fortran/17678] " pinskia at gcc dot gnu dot org
2004-09-27 19:25 ` tobi at gcc dot gnu dot org
2004-09-28 16:01 ` tobi at gcc dot gnu dot org
2004-10-07  0:43 ` cvs-commit at gcc dot gnu dot org
2004-10-07  1:02 ` pinskia at gcc dot gnu dot 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=20040926135843.17678.lei@il.ibm.com \
    --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).