public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "federico.perini at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/106771] [OOP] ICE with PACK intrinsic, in gfc_conv_expr_descriptor, at fortran/trans-array.c:7328
Date: Mon, 29 Aug 2022 18:09:01 +0000	[thread overview]
Message-ID: <bug-106771-4-zIx4d7jgHq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106771-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from federico <federico.perini at gmail dot com> ---
Right: here is a version where the object is initialized: 

https://godbolt.org/z/o566cPG8P

I also see that for the versions that compile (e.g., 11.1.0), there's a weird
SEGFAULT error at this line: 


    elemental logical function isa(this,i)
       class(t), intent(in) :: this
       integer, intent(in) :: i
       integer :: n
       n = merge(size(this%iloc),0,allocated(this%iloc))
       if (i>0 .and. i<=n) then ! Segmentation fault here 
          isa = this%iloc(i)>0
       else
          isa = .false.
       endif  
    end function isa

So it at least compiles, but apparently the bug is hidden somewhere else?

  parent reply	other threads:[~2022-08-29 18:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-29 10:02 [Bug fortran/106771] New: " federico.perini at gmail dot com
2022-08-29 17:21 ` [Bug fortran/106771] " anlauf at gcc dot gnu.org
2022-08-29 17:38 ` anlauf at gcc dot gnu.org
2022-08-29 18:09 ` federico.perini at gmail dot com [this message]
2022-08-29 18:49 ` anlauf at gcc dot gnu.org
2022-08-30  6:57 ` federico.perini at gmail dot com
2022-08-30  7:08 ` rguenth at gcc dot gnu.org
2022-08-30  8:30 ` 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-106771-4-zIx4d7jgHq@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).