public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgomp/110842] [14 Regression] Openmp loops with KIND=16 DO loops Date: Fri, 28 Jul 2023 12:02:34 +0000 [thread overview] Message-ID: <bug-110842-4-0xkD9LyRBf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110842-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110842 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |openmp --- Comment #4 from Tobias Burnus <burnus at gcc dot gnu.org> --- > libgomp has no support for loop iterators larger than 64-bit unsigned, and I believe in OpenMP it is implementation defined which iterator type is used. "The iterations of some number of associated loops can be collapsed into one larger iteration space that is called the logical iteration space. The particular integer type used to compute the iteration count for the collapsed loop is implementation defined, but its bit precision must be at least that of3 the widest type that the implementation would use for the iteration count of each loop if it was the only associated loop." This sounds a bit as if it should be supported – but at the end it is implementation defined. However, I think it makes sense to document it as implementation defined in libomp.texi – and to output a compile time error if we know that something is not implemented. * * * For use the largest type used in the loop, see also OG13-only patch (originally for OG-12): commit https://gcc.gnu.org/g:90d8139007c69657325c5c187b0d47f463b455d1 "openmp: Scale type precision of collapsed iterator variable" But that won't help if libgomp does not support the integer type. * * * > C/C++ OpenMP loops with __int128 or unsigned __int128 iterator will not work either (nor with _BitInt(575) or similar). ... and we likely don't want to support _BitInt iterators!
next prev parent reply other threads:[~2023-07-28 12:02 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-28 10:49 [Bug libgomp/110842] New: " tkoenig at gcc dot gnu.org 2023-07-28 10:55 ` [Bug libgomp/110842] " tkoenig at gcc dot gnu.org 2023-07-28 10:57 ` jakub at gcc dot gnu.org 2023-07-28 11:10 ` tkoenig at gcc dot gnu.org 2023-07-28 12:02 ` burnus at gcc dot gnu.org [this message] 2024-01-10 14:49 ` jamborm at gcc dot gnu.org 2024-03-22 13:42 ` law at gcc dot gnu.org 2024-05-07 7:41 ` [Bug libgomp/110842] [14/15 " rguenth 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-110842-4-0xkD9LyRBf@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).