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 middle-end/94212] Incorrect vectorization of loop with FP calculations
Date: Wed, 18 Mar 2020 12:59:27 +0000	[thread overview]
Message-ID: <bug-94212-4-5S67tl42nw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94212-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #2)
> >(at least x86_64 is fine)
> No, just FMA is not enabled by default.  
> If I use -march=skylake-avx512 , I get the same answers as on aarch64_64.

Note I am running on Intel(R) Xeon(R) D-2146NT CPU @ 2.30GHz.

  parent reply	other threads:[~2020-03-18 12:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-18 12:41 [Bug c/94212] New: [AARCH64] [Regression] " dpochepk at gmail dot com
2020-03-18 12:56 ` [Bug middle-end/94212] " pinskia at gcc dot gnu.org
2020-03-18 12:58 ` pinskia at gcc dot gnu.org
2020-03-18 12:59 ` pinskia at gcc dot gnu.org [this message]
2020-03-18 13:10 ` [Bug middle-end/94212] " pinskia at gcc dot gnu.org
2020-03-18 13:44 ` [Bug tree-optimization/94212] [8/9/10 Regression] " rguenth at gcc dot gnu.org
2020-03-18 14:37 ` dpochepk at gmail dot com
2020-03-18 15:14 ` rguenth at gcc dot gnu.org
2020-03-18 16:49 ` dpochepk at gmail dot com
2021-01-14  8:34 ` [Bug tree-optimization/94212] [8/9/10/11 " rguenth at gcc dot gnu.org
2021-03-26  9:40 ` qianjh at cn dot fujitsu.com
2021-03-26  9:47 ` rguenther at suse dot de
2021-05-14  9:53 ` [Bug tree-optimization/94212] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01  8:16 ` rguenth at gcc dot gnu.org
2022-05-27  9:42 ` [Bug tree-optimization/94212] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:40 ` jakub at gcc dot gnu.org
2022-07-26 13:47 ` 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-94212-4-5S67tl42nw@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).