public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ivan.pribec at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/113305] ICE with do concurrent and ivdep
Date: Wed, 10 Jan 2024 18:24:40 +0000	[thread overview]
Message-ID: <bug-113305-4-vkLrxSdGxs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113305-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113305

--- Comment #3 from Ivan Pribec <ivan.pribec at gmail dot com> ---
In the mail archive
(https://gcc.gnu.org/legacy-ml/fortran/2014-02/msg00077.html) I've read a
message implying that do concurrent gets translated into a regular for-loop
annotated with "#pragma ivdep", which assures the loop optimizer there are no
loop-carried dependencies. That said, I'm aware there is no good reason why
you'd want to use this directive on a do concurrent loop.

  parent reply	other threads:[~2024-01-10 18:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-10 11:00 [Bug fortran/113305] New: " ivan.pribec at gmail dot com
2024-01-10 11:46 ` [Bug fortran/113305] " rguenth at gcc dot gnu.org
2024-01-10 18:15 ` kargl at gcc dot gnu.org
2024-01-10 18:24 ` ivan.pribec at gmail dot com [this message]
2024-01-10 19:43 ` anlauf at gcc dot gnu.org
2024-01-10 19:58 ` sgk at troutmask dot apl.washington.edu
2024-01-10 20:38 ` anlauf at gcc dot gnu.org
2024-01-10 22:25 ` anlauf at gcc dot gnu.org
2024-01-12 20:38 ` anlauf at gcc dot gnu.org
2024-01-13 14:08 ` cvs-commit at gcc dot gnu.org
2024-01-13 21:14 ` anlauf 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-113305-4-vkLrxSdGxs@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).