public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at charter dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/97063] [ MATMUL intrinsic] The value of result is wrong when vector (step size is negative) * matrix
Date: Fri, 18 Sep 2020 22:19:53 +0000 [thread overview]
Message-ID: <bug-97063-4-99gy89iL3Z@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
Jerry DeLisle <jvdelisle at charter dot net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jvdelisle at charter dot net
--- Comment #3 from Jerry DeLisle <jvdelisle at charter dot net> ---
(In reply to anlauf from comment #2)
> Interestingly, the bug "disappears" if frontend optimization is enabled
> (-ffrontend-optimize), thus at all optimizations that enable it.
It could be we need to fix in the runtime library. I have not looked to closely
yet but it would be best I think if the front-end did the necessary
transforming. The code is probably there already to do it.
next prev parent reply other threads:[~2020-09-18 22:19 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 [this message]
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
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-99gy89iL3Z@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).