public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/108546] New: [11/12/13 Regression] ICE in expand_expr_real_1, at expr.cc:10910
Date: Wed, 25 Jan 2023 17:52:01 +0000	[thread overview]
Message-ID: <bug-108546-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 108546
           Summary: [11/12/13 Regression] ICE in expand_expr_real_1, at
                    expr.cc:10910
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gscfq@t-online.de
  Target Milestone: ---

Started with r10, between 20191110 and 20191117 :


$ cat z1.f90
module m
   use iso_c_binding
contains
   subroutine s(x)
      type(c_ptr), optional :: x
      !$omp target is_device_ptr(x)
      if (c_associated(x)) stop
      !$omp end target
   end
end


$ cat z2.f90            # compiles, for reference only
module m
   use iso_c_binding
contains
   subroutine s(x)
      type(c_ptr) :: x
      !$omp target is_device_ptr(x)
      if (c_associated(x)) stop
      !$omp end target
   end
end


$ gfortran-13-20230122 -c z2.f90 -fopenmp
$ gfortran-10-20191110 -c z1.f90 -fopenmp
$
$ gfortran-13-20230122 -c z1.f90 -fopenmp
during RTL pass: expand
z1.f90:6:35:

    6 |       !$omp target is_device_ptr(x)
      |                                   ^
internal compiler error: in expand_expr_real_1, at expr.cc:10910
0xa570bf expand_expr_real_1(tree_node*, rtx_def*, machine_mode,
expand_modifier, rtx_def**, bool)
        ../../gcc/expr.cc:10904
0xa5e66e expand_expr
        ../../gcc/expr.h:310
0xa5e66e expand_operands(tree_node*, tree_node*, rtx_def*, rtx_def**,
rtx_def**, expand_modifier)
        ../../gcc/expr.cc:8582
0xa6a23a do_store_flag
        ../../gcc/expr.cc:13113
0xa6574e expand_expr_real_2(separate_ops*, rtx_def*, machine_mode,
expand_modifier)
        ../../gcc/expr.cc:10259
0x94fba2 expand_gimple_stmt_1
        ../../gcc/cfgexpand.cc:3983
0x94fba2 expand_gimple_stmt
        ../../gcc/cfgexpand.cc:4044
0x9548d7 expand_gimple_basic_block
        ../../gcc/cfgexpand.cc:6096
0x95739e execute
        ../../gcc/cfgexpand.cc:6831

             reply	other threads:[~2023-01-25 17:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-25 17:52 gscfq@t-online.de [this message]
2023-01-26  7:44 ` [Bug fortran/108546] " rguenth at gcc dot gnu.org
2023-01-26  9:43 ` [Bug fortran/108546] [11/12/13 Regression] ICE in expand_expr_real_1, at expr.cc:10910 since r10-4531-ga2c26c50310a3363 marxin at gcc dot gnu.org
2023-02-21 12:56 ` [Bug middle-end/108546] " rguenth at gcc dot gnu.org
2023-03-01 12:53 ` cvs-commit at gcc dot gnu.org
2023-03-08 10:55 ` cvs-commit at gcc dot gnu.org
2023-03-09 11:10 ` cvs-commit at gcc dot gnu.org
2023-03-09 11:11 ` burnus 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-108546-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).