public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/114509] [11/12/13/14 Regression] an infinite loop with openmp after errors in some cases
Date: Thu, 28 Mar 2024 07:03:04 +0000	[thread overview]
Message-ID: <bug-114509-4-ubschqtRBd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114509-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
   Last reconfirmed|                            |2024-03-28
           Keywords|                            |openmp
            Summary|Infinite loop with openmp   |[11/12/13/14 Regression] an
                   |                            |infinite loop with openmp
                   |                            |after errors in some cases
   Target Milestone|---                         |11.5
             Status|UNCONFIRMED                 |NEW
      Known to fail|                            |7.5.0, 9.1.0
          Component|c                           |middle-end
      Known to work|                            |7.2.0, 7.4.0

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
With checking enabled we get:
```
during GIMPLE pass: omplower
t5665.c:11:9: internal compiler error: tree check: expected tree that contains
‘decl minimal’ structure, have ‘error_mark’ in remap_type_1, at
tree-inline.cc:563
   11 | #pragma omp parallel for
      |         ^~~
0x880d2a tree_contains_struct_check_failed(tree_node const*,
tree_node_structure_enum, char const*, int, char const*)
        ../../gcc/tree.cc:9129
0x829211 contains_struct_check(tree_node*, tree_node_structure_enum, char
const*, int, char const*)
        ../../gcc/tree.h:3766
0x829211 remap_type_1
        ../../gcc/tree-inline.cc:563
0x10e3c92 remap_type(tree_node*, copy_body_data*)
        ../../gcc/tree-inline.cc:713
0x10e38ba remap_type_1
        ../../gcc/tree-inline.cc:425
0x10e3c92 remap_type(tree_node*, copy_body_data*)
        ../../gcc/tree-inline.cc:713
0xec7178 fixup_remapped_decl
        ../../gcc/omp-low.cc:905
0xecb9f2 scan_sharing_clauses
        ../../gcc/omp-low.cc:1833
0xecfccb scan_omp_parallel
        ../../gcc/omp-low.cc:2345
0xecfccb scan_omp_1_stmt
        ../../gcc/omp-low.cc:4148
0xd138ea walk_gimple_stmt(gimple_stmt_iterator*, tree_node*
(*)(gimple_stmt_iterator*, bool*, walk_stmt_info*), tree_node* (*)(tree_node**,
int*, void*), walk_stmt_info*)
        ../../gcc/gimple-walk.cc:618
0xd13ac5 walk_gimple_seq_mod(gimple**, tree_node* (*)(gimple_stmt_iterator*,
bool*, walk_stmt_info*), tree_node* (*)(tree_node**, int*, void*),
walk_stmt_info*)
        ../../gcc/gimple-walk.cc:51
0xd139e1 walk_gimple_stmt(gimple_stmt_iterator*, tree_node*
(*)(gimple_stmt_iterator*, bool*, walk_stmt_info*), tree_node* (*)(tree_node**,
int*, void*), walk_stmt_info*)
        ../../gcc/gimple-walk.cc:681
0xd13ac5 walk_gimple_seq_mod(gimple**, tree_node* (*)(gimple_stmt_iterator*,
bool*, walk_stmt_info*), tree_node* (*)(tree_node**, int*, void*),
walk_stmt_info*)
        ../../gcc/gimple-walk.cc:51
0xd139a1 walk_gimple_stmt(gimple_stmt_iterator*, tree_node*
(*)(gimple_stmt_iterator*, bool*, walk_stmt_info*), tree_node* (*)(tree_node**,
int*, void*), walk_stmt_info*)
        ../../gcc/gimple-walk.cc:735
0xd13ac5 walk_gimple_seq_mod(gimple**, tree_node* (*)(gimple_stmt_iterator*,
bool*, walk_stmt_info*), tree_node* (*)(tree_node**, int*, void*),
walk_stmt_info*)
        ../../gcc/gimple-walk.cc:51
0xedc43a scan_omp
        ../../gcc/omp-low.cc:4284
0xedc43a execute_lower_omp
        ../../gcc/omp-low.cc:14619
0xedc43a execute
        ../../gcc/omp-low.cc:14683
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
```

  reply	other threads:[~2024-03-28  7:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-28  6:39 [Bug c/114509] New: Infinite loop with openmp gccbugs at dima dot secretsauce.net
2024-03-28  7:03 ` pinskia at gcc dot gnu.org [this message]
2024-03-29 23:48 ` [Bug middle-end/114509] [11/12/13/14 Regression] an infinite loop or ICE with openmp after errors in some cases law at gcc dot gnu.org
2024-04-02  8:01 ` rguenth at gcc dot gnu.org
2024-04-17 14:42 ` 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-114509-4-ubschqtRBd@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).