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/99218] [8/9/10/11 Regression] matmul on temporary array accesses invalid memory (segfault)
Date: Fri, 05 Mar 2021 19:59:58 +0000	[thread overview]
Message-ID: <bug-99218-4-3U1xjgkjt0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99218-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Harald Anlauf <anlauf@gcc.gnu.org>:

https://gcc.gnu.org/g:b1bee29167df6b0fbc9a4c8d06e2acbf3367af47

commit r11-7531-gb1bee29167df6b0fbc9a4c8d06e2acbf3367af47
Author: Harald Anlauf <anlauf@gmx.de>
Date:   Fri Mar 5 20:57:54 2021 +0100

    PR libfortran/99218 - matmul on temporary array accesses invalid memory

    Do not invoke tuned rank-2 times rank-2 matmul if rank(b) == 1.

    libgfortran/ChangeLog:

            PR libfortran/99218
            * m4/matmul_internal.m4: Invoke tuned matmul only for rank(b)>1.
            * 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:

            PR libfortran/99218
            * gfortran.dg/matmul_21.f90: New test.

  parent reply	other threads:[~2021-03-05 19:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-23 14:16 [Bug fortran/99218] New: " rpmcnally at gmail dot com
2021-02-23 20:07 ` [Bug fortran/99218] " anlauf at gcc dot gnu.org
2021-02-23 20:27 ` anlauf at gcc dot gnu.org
2021-02-23 21:10 ` anlauf at gcc dot gnu.org
2021-02-23 21:18 ` [Bug libfortran/99218] [8/9/19/11 Regression] " anlauf at gcc dot gnu.org
2021-02-23 21:47 ` anlauf at gcc dot gnu.org
2021-02-23 21:47 ` [Bug libfortran/99218] [8/9/10/11 " anlauf at gcc dot gnu.org
2021-03-05 19:59 ` cvs-commit at gcc dot gnu.org [this message]
2021-03-06 17:23 ` cvs-commit at gcc dot gnu.org
2021-03-07 19:42 ` cvs-commit at gcc dot gnu.org
2021-03-07 20:27 ` cvs-commit at gcc dot gnu.org
2021-03-07 20:28 ` 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-99218-4-3U1xjgkjt0@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).