public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/96133] [10/11 Regression] x86-64 gcc 10.1 using -O3 leads to wrong calculation since r10-1882-g831e688af50c5f77
Date: Thu, 09 Jul 2020 12:06:04 +0000	[thread overview]
Message-ID: <bug-96133-4-v4TmJfN2bV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96133-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed.  The i == 1 lane is different.  We're using standard interleaving
vectorization here, the innermost two loops are unrolled and rgb_cam is elided.

Note eventually we optimize the whole loop at compile-time to

  <bb 2> [local count: 89478486]:
  MEM <vector(2) double> [(double *)&xyz_cam] = {
2.97789709999999985257090884260833263397216796875e+0,
3.94211709999999992959374139900319278240203857421875e+0 };
  MEM <vector(2) double> [(double *)&xyz_cam + 16B] = {
4.9063371000000000066165739553980529308319091796875e+0,
3.291832700000000055950977184693329036235809326171875e+0 };
  MEM <vector(2) double> [(double *)&xyz_cam + 32B] = {
4.06932820000000017301999832852743566036224365234375e+0,
4.8468236999999998459998096222989261150360107421875e+0 };
  MEM <vector(2) double> [(double *)&xyz_cam + 48B] = {
5.40156330000000028945805752300657331943511962890625e+0,
6.2267732999999996224005371914245188236236572265625e+0 };
  xyz_cam[2][2] = 7.051983299999999843521436559967696666717529296875e+0;

  parent reply	other threads:[~2020-07-09 12:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-09 11:38 [Bug c++/96133] New: x86-64 gcc 10.1 using -O3 leads to wrong calculation heckflosse67 at gmx dot de
2020-07-09 12:01 ` [Bug c++/96133] [10/11 Regression] x86-64 gcc 10.1 using -O3 leads to wrong calculation since r10-1882-g831e688af50c5f77 marxin at gcc dot gnu.org
2020-07-09 12:06 ` rguenth at gcc dot gnu.org [this message]
2020-07-09 12:06 ` [Bug tree-optimization/96133] " rguenth at gcc dot gnu.org
2020-07-09 12:13 ` rguenth at gcc dot gnu.org
2020-07-09 12:18 ` rguenth at gcc dot gnu.org
2020-07-09 17:54 ` cvs-commit at gcc dot gnu.org
2020-07-09 17:55 ` rguenth at gcc dot gnu.org
2020-07-09 19:33 ` heckflosse67 at gmx dot de
2020-07-10  7:30 ` rguenth at gcc dot gnu.org
2020-07-10  8:53 ` cvs-commit at gcc dot gnu.org
2020-07-10 10:38 ` [Bug tree-optimization/96133] [10 " cvs-commit at gcc dot gnu.org
2020-07-10 10:38 ` rguenth at gcc dot gnu.org
2020-07-10 11:36 ` heckflosse67 at gmx dot de

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-96133-4-v4TmJfN2bV@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).