public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/113409] ICE: in omp_extract_for_data, at omp-general.cc:411 with -fopenmp-simd and _BitInt() Date: Tue, 16 Jan 2024 12:10:26 +0000 [thread overview] Message-ID: <bug-113409-4-yBx4kZpYr0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113409-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113409 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |burnus at gcc dot gnu.org --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> --- On e.g. void bar (_BitInt(931)); void foo (_BitInt(931) x) { #pragma omp parallel for for (_BitInt(931) i = 0; i < x; ++i) bar (i); } clang emits warning: OpenMP loop iteration variable cannot have more than 64 bits size and will be narrowed [-Wopenmp-loop-form] warning. On void bar (__int128); void foo (__int128 x) { #pragma omp parallel for // schedule(runtime) for (__int128 i = 0; i < x; ++i) bar (i); } we actually emit something that probably works and with schedule(runtime) silently assume it won't be more than 64-bit of iterations. So supposedly we should treat BITINT_TYPEs the same.
next prev parent reply other threads:[~2024-01-16 12:10 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-15 20:37 [Bug tree-optimization/113409] New: " zsojka at seznam dot cz 2024-01-16 12:10 ` jakub at gcc dot gnu.org [this message] 2024-01-16 13:13 ` [Bug middle-end/113409] " jakub at gcc dot gnu.org 2024-01-16 15:13 ` jakub at gcc dot gnu.org 2024-01-17 9:51 ` cvs-commit at gcc dot gnu.org 2024-01-17 10:37 ` jakub at gcc dot gnu.org 2024-01-20 17:11 ` pinskia 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-113409-4-yBx4kZpYr0@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).