public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gccbugs at dima dot secretsauce.net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/114509] New: Infinite loop with openmp Date: Thu, 28 Mar 2024 06:39:46 +0000 [thread overview] Message-ID: <bug-114509-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114509 Bug ID: 114509 Summary: Infinite loop with openmp Product: gcc Version: 13.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: gccbugs at dima dot secretsauce.net Target Milestone: --- Created attachment 57827 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57827&action=edit Reduced reproducer I git a bug in gcc 13.2 where an openmp loop causes he compiler to spin the cpu, and never finish. I used creduce to minimize the test case, and the reduced source is attached. I'm running Debian GNU/Linux with gcc=4:13.2.0-1. I get an infinite loop with gcc-13 -fopenmp -c -o /dev/null /tmp/infinite-openmp.c I happen to also have gcc-10 and gcc-11 installed, and they both produce an infinite loop with that input as well. Thanks
next reply other threads:[~2024-03-28 6:39 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-28 6:39 gccbugs at dima dot secretsauce.net [this message] 2024-03-28 7:03 ` [Bug middle-end/114509] [11/12/13/14 Regression] an infinite loop with openmp after errors in some cases pinskia at gcc dot gnu.org 2024-03-29 23:48 ` [Bug middle-end/114509] [11/12/13/14 Regression] an infinite loop or ICE " 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@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: linkBe 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).