public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sandra at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/103390] [12 Regression] ICE: gimplification failed since r12-4591-g1af78e731feb9327
Date: Thu, 30 Dec 2021 19:30:48 +0000	[thread overview]
Message-ID: <bug-103390-4-UcboimhNQw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103390-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from sandra at gcc dot gnu.org ---
I thought I had a fix for this that involved making gfc_is_simply_contiguous
smarter about intrinsics and other function calls, but after writing more test
cases I found that this one still ICEs.

program p
   integer, pointer :: z(:)
   integer :: a(3) = [1, 2, 3];
   integer :: b(3) = [4, 5, 6];
   call s(a + b);
contains
   subroutine s(x) bind(c)
      integer, contiguous :: x(:)
   end
end

Tobias's other suggestion to me was gating the copy-out code with
gfc_expr_is_variable() so I'll try that next.

  parent reply	other threads:[~2021-12-30 19:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-23 18:57 [Bug fortran/103390] New: [12 Regression] ICE: gimplification failed gscfq@t-online.de
2021-11-24  8:38 ` [Bug fortran/103390] [12 Regression] ICE: gimplification failed since r12-4591-g1af78e731feb9327 marxin at gcc dot gnu.org
2021-11-24  8:53 ` rguenth at gcc dot gnu.org
2021-12-14  1:44 ` sandra at gcc dot gnu.org
2021-12-14  1:47 ` sandra at gcc dot gnu.org
2021-12-30 19:30 ` sandra at gcc dot gnu.org [this message]
2022-01-01 23:10 ` sandra at gcc dot gnu.org
2022-01-02 18:37 ` sandra at gcc dot gnu.org
2022-01-03 11:58 ` antony at cosmologist dot info
2022-01-03 16:48 ` cvs-commit at gcc dot gnu.org
2022-01-03 17:01 ` sandra at gcc dot gnu.org
2022-01-03 18:43 ` antony at cosmologist dot info
2022-01-05 17:05 ` sandra 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-103390-4-UcboimhNQw@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).