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/107214] New: [13 Regression] ICE: base pointer cycle detected
Date: Tue, 11 Oct 2022 16:53:02 +0000	[thread overview]
Message-ID: <bug-107214-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 107214
           Summary: [13 Regression] ICE: base pointer cycle detected
           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 between 20220911 and 20220918 :


$ cat z1.f90
program p
   integer, allocatable :: a
   !$omp target map(tofrom: a, a)
   !$omp end target
end


$ gfortran-13-20221009 -c z1.f90 -fopenmp
when processing group:
map(tofrom:*a) map(alloc:a [pointer assign, bias: 0])
z1.f90:3:33:

    3 |    !$omp target map(tofrom: a, a)
      |                                 ^
internal compiler error: base pointer cycle detected
0xaee0b3 omp_tsort_mapping_groups_1
        ../../gcc/gimplify.cc:9571
0xaeded5 omp_tsort_mapping_groups_1
        ../../gcc/gimplify.cc:9614
0xb02820 omp_tsort_mapping_groups
        ../../gcc/gimplify.cc:9652
0xb02820 gimplify_scan_omp_clauses
        ../../gcc/gimplify.cc:10739
0xb08a0e gimplify_omp_workshare
        ../../gcc/gimplify.cc:15357
0xaf47ab gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*),
int)
        ../../gcc/gimplify.cc:16870
0xaf7ad8 gimplify_stmt(tree_node**, gimple**)
        ../../gcc/gimplify.cc:7187
0xaf59cb gimplify_statement_list
        ../../gcc/gimplify.cc:2021
0xaf59cb gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*),
int)
        ../../gcc/gimplify.cc:16773
0xaf7ad8 gimplify_stmt(tree_node**, gimple**)
        ../../gcc/gimplify.cc:7187
0xaf8031 gimplify_bind_expr
        ../../gcc/gimplify.cc:1430
0xaf503b gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*),
int)
        ../../gcc/gimplify.cc:16529
0xaf7ad8 gimplify_stmt(tree_node**, gimple**)
        ../../gcc/gimplify.cc:7187
0xaf8b7b gimplify_body(tree_node*, bool)
        ../../gcc/gimplify.cc:17588
0xaf8fcd gimplify_function_tree(tree_node*)
        ../../gcc/gimplify.cc:17787
0x9808d7 cgraph_node::analyze()
        ../../gcc/cgraphunit.cc:676
0x983267 analyze_functions
        ../../gcc/cgraphunit.cc:1240
0x983c1d symbol_table::finalize_compilation_unit()
        ../../gcc/cgraphunit.cc:2500

             reply	other threads:[~2022-10-11 16:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-11 16:53 gscfq@t-online.de [this message]
2022-10-12  7:49 ` [Bug fortran/107214] [13 Regression] ICE: base pointer cycle detected since r13-2661-gb57abd072dd319a7 marxin at gcc dot gnu.org
2022-10-14  7:15 ` rguenth at gcc dot gnu.org
2022-10-18  8:06 ` rguenth at gcc dot gnu.org
2022-12-14 14:12 ` cvs-commit at gcc dot gnu.org
2023-01-17 20:45 ` anlauf at gcc dot gnu.org
2023-02-06 13:29 ` jakub 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-107214-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).