public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/97063] [ MATMUL intrinsic] The value of result is wrong when vector (step size is negative) * matrix
Date: Sat, 24 Oct 2020 20:09:47 +0000 [thread overview]
Message-ID: <bug-97063-4-LB64RgyXIR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97063-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97063
--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Harald Anlauf
<anlauf@gcc.gnu.org>:
https://gcc.gnu.org/g:8d3b261f250a3863d886ae845e47f235d301fb09
commit r9-9010-g8d3b261f250a3863d886ae845e47f235d301fb09
Author: Harald Anlauf <anlauf@gmx.de>
Date: Sun Oct 18 20:15:26 2020 +0200
PR libfortran/97063 - Wrong result for vector (step size is negative) *
matrix
The MATMUL intrinsic provided a wrong result for rank-1 times rank-2 array
when a negative stride was used for addressing the elements of the rank-1
array, because a check on strides was erroneously placed before the check
on the rank. Interchange order of checks.
libgfortran/ChangeLog:
* m4/matmul_internal.m4: Move check for rank-1 times rank-2 before
checks on strides for rank-2 times rank-2.
* generated/matmul_c10.c: Regenerated.
* generated/matmul_c16.c: Likewise.
* generated/matmul_c4.c: Likewise.
* generated/matmul_c8.c: Likewise.
* generated/matmul_i1.c: Likewise.
* generated/matmul_i16.c: Likewise.
* generated/matmul_i2.c: Likewise.
* generated/matmul_i4.c: Likewise.
* generated/matmul_i8.c: Likewise.
* generated/matmul_r10.c: Likewise.
* generated/matmul_r16.c: Likewise.
* generated/matmul_r4.c: Likewise.
* generated/matmul_r8.c: Likewise.
* generated/matmulavx128_c10.c: Likewise.
* generated/matmulavx128_c16.c: Likewise.
* generated/matmulavx128_c4.c: Likewise.
* generated/matmulavx128_c8.c: Likewise.
* generated/matmulavx128_i1.c: Likewise.
* generated/matmulavx128_i16.c: Likewise.
* generated/matmulavx128_i2.c: Likewise.
* generated/matmulavx128_i4.c: Likewise.
* generated/matmulavx128_i8.c: Likewise.
* generated/matmulavx128_r10.c: Likewise.
* generated/matmulavx128_r16.c: Likewise.
* generated/matmulavx128_r4.c: Likewise.
* generated/matmulavx128_r8.c: Likewise.
gcc/testsuite/ChangeLog:
* gfortran.dg/matmul_20.f90: New test.
(cherry picked from commit cd6cd6aed195b4ec7d652e8b41d60b60e174304e)
next prev parent reply other threads:[~2020-10-24 20:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 1:00 [Bug fortran/97063] New: " xin.liu@compiler-dev.com
2020-09-18 20:42 ` [Bug fortran/97063] " anlauf at gcc dot gnu.org
2020-09-18 20:49 ` anlauf at gcc dot gnu.org
2020-09-18 22:19 ` jvdelisle at charter dot net
2020-09-22 19:42 ` anlauf at gcc dot gnu.org
2020-10-11 17:59 ` [Bug libfortran/97063] " anlauf at gcc dot gnu.org
2020-10-11 19:10 ` anlauf at gcc dot gnu.org
2020-10-18 18:16 ` cvs-commit at gcc dot gnu.org
2020-10-19 21:07 ` cvs-commit at gcc dot gnu.org
2020-10-24 20:09 ` cvs-commit at gcc dot gnu.org [this message]
2020-10-24 20:14 ` cvs-commit at gcc dot gnu.org
2020-10-24 20:16 ` 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-97063-4-LB64RgyXIR@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).