public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zed.three at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/105658] New: Passing array component to unlimited polymorphic routine passes wrong slice
Date: Thu, 19 May 2022 09:28:10 +0000	[thread overview]
Message-ID: <bug-105658-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105658

            Bug ID: 105658
           Summary: Passing array component to unlimited polymorphic
                    routine passes wrong slice
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: zed.three at gmail dot com
  Target Milestone: ---

The following program:

    program f
    implicit none

    type :: foo
        integer :: member1
        integer :: member2
    end type foo

    type(foo), dimension(3) :: thing = [foo(1, 2), foo(3, 4), foo(5, 6)]

    call print_poly(thing%member1)
    call print_int(thing%member1)

    contains
        subroutine print_poly(array)
            class(*), dimension(:), intent(in) :: array

            select type(array)
            type is (integer)
                print*, array
            end select
        end subroutine

        subroutine print_int(array)
            integer, dimension(:), intent(in) :: array

            print*, array
        end subroutine
    end program f

prints:

           1           2           3
           1           3           5

when we would expect:

           1           3           5
           1           3           5

Adding `-fcheck=all`, we get the warning "Fortran runtime warning: An array
temporary was created" _only_ for the call to `print_int`.

Adding an extra set of parentheses to the `print_poly` call (`call
print_poly((thing%member1))` gives the expected behaviour, I guess because it's
forcing an array temporary?

This behaviour is present in 4.9.4 through to the trunk currently available on
Compiler Explorer
((Compiler-Explorer-Build-gcc-7da9a089608b0ca09683332ce014fb6184842724-binutils-2.38)
13.0.0 20220518 (experimental))

             reply	other threads:[~2022-05-19  9:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-19  9:28 zed.three at gmail dot com [this message]
2024-02-20 19:50 ` [Bug fortran/105658] " cvs-commit at gcc dot gnu.org
2024-02-20 19:57 ` anlauf at gcc dot gnu.org
2024-03-06 21:12 ` anlauf 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-105658-4@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).