public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tkoenig 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 11:10:36 +0000	[thread overview]
Message-ID: <bug-110842-4-jDnE1UVVqd@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

--- Comment #3 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #2)
> Why a regression?

It worked before (if only by accident), hence I put "Regression" there.

> 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.
> C/C++ OpenMP loops with __int128 or unsigned __int128 iterator will not work
> either (nor with _BitInt(575) or similar).

If it is illegal, then the best way to do this would probably be an error
message instead of silent wrong code.

  parent reply	other threads:[~2023-07-28 11:10 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 [this message]
2023-07-28 12:02 ` burnus at gcc dot gnu.org
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-jDnE1UVVqd@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).