public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "reiter.christoph at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgomp/105745] New: Conditional OpenMP directive fails with GCC 12 Date: Thu, 26 May 2022 21:10:25 +0000 [thread overview] Message-ID: <bug-105745-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105745 Bug ID: 105745 Summary: Conditional OpenMP directive fails with GCC 12 Product: gcc Version: 12.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libgomp Assignee: unassigned at gcc dot gnu.org Reporter: reiter.christoph at gmail dot com CC: jakub at gcc dot gnu.org Target Milestone: --- Downstream issue: https://github.com/msys2/MINGW-packages/issues/11729 The following example crashes with GCC 12.1.0, but works fine with GCC 11.3.0: // g++ -fopenmp -o broken.exe broken.c; ./broken.exe; echo $? int main() { #pragma omp parallel for if (0) for (int idx = 0; idx < 0; ++idx) { } return 0; } * Removing the "if (0)" condition makes it work again * Replacing libgomp-1.dll with the one from GCC 11.3 also makes things work again. * Another example that crashes is "#pragma omp for schedule(dynamic)" This is on 32/64 bit Windows.
next reply other threads:[~2022-05-26 21:10 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-26 21:10 reiter.christoph at gmail dot com [this message] 2022-05-27 3:06 ` [Bug target/105745] " pinskia at gcc dot gnu.org 2022-05-27 6:32 ` [Bug target/105745] [12/13 Regression] " rguenth at gcc dot gnu.org 2022-05-27 6:38 ` reiter.christoph at gmail dot com 2022-05-27 6:48 ` reiter.christoph at gmail dot com 2022-05-27 8:25 ` reiter.christoph at gmail dot com 2022-05-27 9:07 ` jakub at gcc dot gnu.org 2022-05-27 9:17 ` reiter.christoph at gmail dot com 2022-05-27 9:17 ` reiter.christoph at gmail dot com 2022-05-27 9:23 ` reiter.christoph at gmail dot com 2022-05-27 11:19 ` [Bug libgomp/105745] " jakub at gcc dot gnu.org 2022-05-27 11:29 ` reiter.christoph at gmail dot com 2022-05-28 6:33 ` cvs-commit at gcc dot gnu.org 2022-05-30 3:36 ` cvs-commit at gcc dot gnu.org 2022-05-30 7:58 ` 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-105745-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).