public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/45004] [OOP] Segfault with allocatable scalars and move_alloc
Date: Thu, 22 Jul 2010 21:45:00 -0000	[thread overview]
Message-ID: <20100722214454.19673.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45004-9410@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from janus at gcc dot gnu dot org  2010-07-22 21:44 -------
Here is an even more elementary example which shows that there is a problem for
allocatable scalars, already without any polymorphic variables:

  implicit none
  integer, allocatable :: afab1,afab2
  allocate(afab1)
  afab1 = irand()
  print *,afab1
  call move_alloc(afab1, afab2)
  print *,afab2
  print *,allocated(afab2)
  print *,allocated(afab1)
end


This directly segfaults on move_alloc:

       16807
Segmentation fault


The problem is that _gfortran_move_alloc expects two array descriptors as
arguments, but allocatable scalars have none. Therefore we probably need
something like '_gfortran_move_alloc_scalar'.

For classes we will probably have to add a reference to the $data component
before passing them to move_alloc.


-- 


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


  parent reply	other threads:[~2010-07-22 21:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-20 12:52 [Bug fortran/45004] New: " sfilippone at uniroma2 dot it
2010-07-20 12:53 ` [Bug fortran/45004] " sfilippone at uniroma2 dot it
2010-07-22 21:22 ` janus at gcc dot gnu dot org
2010-07-22 21:45 ` janus at gcc dot gnu dot org [this message]
2010-07-23 16:20 ` janus at gcc dot gnu dot org
2010-07-29 18:15 ` janus at gcc dot gnu dot org
2010-07-29 18:18 ` janus 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=20100722214454.19673.qmail@sourceware.org \
    --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).