public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/46244] gfc_compare_derived_types is buggy
Date: Sun, 20 Feb 2011 22:20:00 -0000	[thread overview]
Message-ID: <bug-46244-4-dGpdukvhR6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46244-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #14 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2011-02-20 22:01:54 UTC ---
> (apparently this new feature is not tested in the test suite)

This wrong, there are several tests;-) The one that is missing is of the form:


module psb_base_mat_mod
  type  :: psb_base_sparse_mat
    integer, private     :: m, n
    integer, private     :: state, duplicate 
    logical, private     :: triangle, unitd, upper, sorted
  end type psb_base_sparse_mat
end module psb_base_mat_mod

module psb_d_base_mat_mod
  use psb_base_mat_mod
  integer, parameter  :: psb_dpk_ = kind(1.d0)
  type, extends(psb_base_sparse_mat) :: psb_d_base_sparse_mat
  end type psb_d_base_sparse_mat

  type, extends(psb_d_base_sparse_mat) :: psb_d_coo_sparse_mat
    integer              :: nnz
    integer, allocatable :: ia(:), ja(:)
    real(psb_dpk_), allocatable :: val(:)
  end type psb_d_coo_sparse_mat

end module psb_d_base_mat_mod

module psb_d_mat_mod
  use psb_d_base_mat_mod
  type :: psb_d_sparse_mat
    class(psb_d_base_sparse_mat), allocatable  :: a 
  contains
    procedure, pass(a) :: d_csclip
    generic, public    :: csclip =>  d_csclip
  end type psb_d_sparse_mat

contains 

  subroutine d_csclip(a,b,info)
    use psb_d_base_mat_mod
    implicit none

    class(psb_d_sparse_mat), intent(in) :: a
    class(psb_d_sparse_mat), intent(out) :: b
    integer,intent(out)                  :: info
    type(psb_d_coo_sparse_mat), allocatable  :: acoo

    info = 0
    allocate(acoo,stat=info)    
    if (info == 0) call move_alloc(acoo,b%a)

  end subroutine d_csclip

end module psb_d_mat_mod


  parent reply	other threads:[~2011-02-20 22:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-30 14:24 [Bug fortran/46244] New: " janus at gcc dot gnu.org
2010-10-30 14:30 ` [Bug fortran/46244] " janus at gcc dot gnu.org
2010-10-30 14:54 ` janus at gcc dot gnu.org
2010-10-30 15:04 ` janus at gcc dot gnu.org
2010-10-30 15:11 ` janus at gcc dot gnu.org
2010-10-30 16:02 ` mikael at gcc dot gnu.org
2010-10-30 16:04 ` mikael at gcc dot gnu.org
2010-11-05 13:56 ` dominiq at lps dot ens.fr
2010-11-05 15:01 ` burnus at gcc dot gnu.org
2010-11-06 13:00 ` burnus at gcc dot gnu.org
2010-11-10 17:45 ` burnus at gcc dot gnu.org
2010-11-10 17:49 ` burnus at gcc dot gnu.org
2011-02-20 16:58 ` mikael at gcc dot gnu.org
2011-02-20 17:01 ` mikael at gcc dot gnu.org
2011-02-20 21:07 ` dominiq at lps dot ens.fr
2011-02-20 22:20 ` dominiq at lps dot ens.fr [this message]
2011-02-20 23:18 ` mikael at gcc dot gnu.org
2011-02-21  9:37 ` paul.richard.thomas at gmail dot com
2011-10-02 17:47 ` dominiq at lps dot ens.fr
2011-10-02 22:06 ` mikael at gcc dot gnu.org
2024-01-19 18:00 ` mikael 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-46244-4-dGpdukvhR6@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).