public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "matthew.thompson at nasa dot gov" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/59093] Segfault in gfc_trans_pointer_assignment
Date: Wed, 26 Mar 2014 18:29:00 -0000	[thread overview]
Message-ID: <bug-59093-4-eqmpJuE7DU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59093-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Matt Thompson <matthew.thompson at nasa dot gov> ---
An additional thought. You have a reduced test case which dies in Comment #3
(which fails for gfortran 4.9). However, you can make something similar which
succeeds:
****
program main

implicit none

type :: MAPL_LocStream
  type(MAPL_LocStreamType), pointer :: Ptr
end type

type MAPL_Tiling
   integer :: IM
end type

type MAPL_LocStreamType
   type(MAPL_Tiling), pointer  :: Tiling(:)
end type

contains

  subroutine MAPL_LocStreamGet (GRIDIM)
    type(MAPL_LocStream) :: LocStream
    integer, pointer     :: GRIDIM(:)

    integer, pointer     :: LP(:)

    LP => LocStream%Ptr%Tiling(:)%IM

  end subroutine

end program main
****

So, it's not that gfortran/gcc can't do the pointer, it's that it can't do it
to a pointer passed through the interface. Note that this still fails:

****
program main

implicit none

type :: MAPL_LocStream
  type(MAPL_LocStreamType), pointer :: Ptr
end type

type MAPL_Tiling
   integer :: IM
end type

type MAPL_LocStreamType
   type(MAPL_Tiling), pointer  :: Tiling(:)
end type

contains

  subroutine MAPL_LocStreamGet (GRIDIM)
    type(MAPL_LocStream) :: LocStream
    integer, pointer     :: GRIDIM(:)

    integer, pointer     :: LP(:)

    LP => LocStream%Ptr%Tiling(:)%IM
    GRIDIM => LP

  end subroutine

end program main
****
with:
$ gfortran --version
GNU Fortran (GCC) 4.9.0 20140105 (experimental)
Copyright (C) 2014 Free Software Foundation, Inc.

GNU Fortran comes with NO WARRANTY, to the extent permitted by law.
You may redistribute copies of GNU Fortran
under the terms of the GNU General Public License.
For more information about these matters, see the file named COPYING

$ gfortran test.fix.F90
test.fix.F90: In function ‘mapl_locstreamget’:
test.fix.F90:26:0: internal compiler error: Segmentation fault
     GRIDIM => LP
 ^
0x50ff58 ???
    ../sysdeps/x86_64/elf/start.S:113
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.
>From gcc-bugs-return-447579-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Mar 26 18:32:30 2014
Return-Path: <gcc-bugs-return-447579-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31823 invoked by alias); 26 Mar 2014 18:32:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 31790 invoked by uid 48); 26 Mar 2014 18:32:27 -0000
From: "david.abdurachmanov at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/60675] [4.9 regression][aarch64] internal compiler error: Max. number of generated reload insns per insn is achieved (90)
Date: Wed, 26 Mar 2014 18:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: david.abdurachmanov at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-60675-4-LyrjL8HrIb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-60675-4@http.gcc.gnu.org/bugzilla/>
References: <bug-60675-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-03/txt/msg02448.txt.bz2
Content-length: 166

http://gcc.gnu.org/bugzilla/show_bug.cgi?id`675

--- Comment #3 from David Abdurachmanov <david.abdurachmanov at gmail dot com> ---
With `-mno-lra` compiles fine.


  parent reply	other threads:[~2014-03-26 18:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-12 20:16 [Bug fortran/59093] New: internal compiler error: Segmentation fault compiling F90 File matthew.thompson at nasa dot gov
2013-11-12 20:58 ` [Bug fortran/59093] " dominiq at lps dot ens.fr
2013-11-12 21:13 ` dominiq at lps dot ens.fr
2014-01-04 17:17 ` janus at gcc dot gnu.org
2014-03-19 19:04 ` [Bug fortran/59093] Segfault in gfc_trans_pointer_assignment matthew.thompson at nasa dot gov
2014-03-26 18:29 ` matthew.thompson at nasa dot gov [this message]
2014-06-11 11:50 ` matthew.thompson at nasa dot gov
2015-01-25 21:30 ` anlauf at gmx dot de
2015-05-21 16:12 ` matthew.thompson at nasa dot gov

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-59093-4-eqmpJuE7DU@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).