public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit 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: Wed, 17 Jan 2024 09:51:13 +0000	[thread overview]
Message-ID: <bug-113409-4-3c9Q8FIv8G@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

--- Comment #4 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:c8f10456795c84bdbf45b1612321eb1f9b3c1415

commit r14-8178-gc8f10456795c84bdbf45b1612321eb1f9b3c1415
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Wed Jan 17 10:47:31 2024 +0100

    openmp: Add OpenMP _BitInt support [PR113409]

    The following patch adds support for _BitInt iterators of OpenMP canonical
    loops (with the preexisting limitation that when not using compile time
    static scheduling the iterators in the library are at most unsigned long
long
    or signed long, so one can't in the runtime/dynamic/guided etc. cases
iterate
    more than what those types can represent, like is the case of e.g. __int128
    iterators too) and the testcase also covers linear/reduction clauses for
them.

    2024-01-17  Jakub Jelinek  <jakub@redhat.com>

            PR middle-end/113409
            * omp-general.cc (omp_adjust_for_condition): Handle BITINT_TYPE
like
            INTEGER_TYPE.
            (omp_extract_for_data): Use build_bitint_type rather than
            build_nonstandard_integer_type if either iter_type or loop->v type
            is BITINT_TYPE.
            * omp-expand.cc (expand_omp_for_generic,
            expand_omp_taskloop_for_outer, expand_omp_taskloop_for_inner):
Handle
            BITINT_TYPE like INTEGER_TYPE.

            * testsuite/libgomp.c/bitint-1.c: New test.

  parent reply	other threads:[~2024-01-17  9:51 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 ` [Bug middle-end/113409] " jakub at gcc dot gnu.org
2024-01-16 13:13 ` 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 [this message]
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-3c9Q8FIv8G@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).