public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kugan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/114653] Not vectorizing the loop with openmp reduction. Date: Wed, 10 Apr 2024 06:48:24 +0000 [thread overview] Message-ID: <bug-114653-4-cdqBbTdBfB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114653-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114653 --- Comment #5 from kugan at gcc dot gnu.org --- ddd for the : ref_a: _57 = D.4803[_20]; ref_b: D.4803[_20] = _ifc__174; We get DDR_ARE_DEPENDENT (ddr) == chrec_dont_know. Hence apply_safelen ().
next prev parent reply other threads:[~2024-04-10 6:48 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-09 9:53 [Bug middle-end/114653] New: Not vectoring " kugan at gcc dot gnu.org 2024-04-09 12:53 ` [Bug middle-end/114653] Not vectorizing " rguenth at gcc dot gnu.org 2024-04-10 3:55 ` kugan at gcc dot gnu.org 2024-04-10 3:58 ` kugan at gcc dot gnu.org 2024-04-10 5:05 ` kugan at gcc dot gnu.org 2024-04-10 6:48 ` kugan at gcc dot gnu.org [this message] 2024-04-10 6:53 ` kugan 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-114653-4-cdqBbTdBfB@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).