public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/61245] #pragma GCC ivdep is ignored with call inside the test of a for loop
Date: Sun, 20 Jun 2021 09:38:06 +0000	[thread overview]
Message-ID: <bug-61245-4-DfqgMBQyaA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61245-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
The loop is still vectorized though. As it looks like it was versioned.

t6.cc: In function ‘void doT(SoA<N>&) [with int N = 3]’:
t6.cc:34:17: warning: ignoring loop annotation
   34 |   for (auto i=0U; i<soa.size(); ++i)
      |                 ^
t6.cc:10:17: optimized: loop vectorized using 16 byte vectors
t6.cc:10:17: optimized: loop vectorized using 8 byte vectors
t6.cc:34:17: optimized: loop vectorized using 16 byte vectors
t6.cc:34:17: optimized:  loop versioned for vectorization because of possible
aliasing
t6.cc:34:17: optimized: loop vectorized using 8 byte vectors

I don't know how useful "#pragma GCC ivdep" is these days really.

  parent reply	other threads:[~2021-06-20  9:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-20  7:29 [Bug tree-optimization/61245] New: ICE at in expand_ANNOTATE, at internal-fn.c:127 called from cfgexpand.c vincenzo.innocente at cern dot ch
2014-05-20  8:18 ` [Bug middle-end/61245] " rguenth at gcc dot gnu.org
2014-05-20  8:24 ` [Bug c++/61245] " rguenth at gcc dot gnu.org
2021-06-20  9:30 ` pinskia at gcc dot gnu.org
2021-06-20  9:34 ` [Bug c++/61245] #pragma GCC ivdep is ignored with call inside the test of a for loop pinskia at gcc dot gnu.org
2021-06-20  9:38 ` pinskia at gcc dot gnu.org [this message]
2021-07-31 22:07 ` pinskia at gcc dot gnu.org
2021-08-02  6:45 ` [Bug c++/61245] #pragma GCC ivdep is handled incorrectly inside templates 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-61245-4-DfqgMBQyaA@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).