From: Tobias Burnus <tobias@codesourcery.com>
To: Richard Biener <richard.guenther@gmail.com>,
Steve Kargl <sgk@troutmask.apl.washington.edu>
Cc: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
Thomas Koenig <tkoenig@netcologne.de>
Subject: Re: MATMUL broken with frontend optimization.
Date: Thu, 18 Mar 2021 15:48:08 +0100 [thread overview]
Message-ID: <563cee48-fbcc-09bc-0cd1-f05082e4feb3@codesourcery.com> (raw)
In-Reply-To: <CAFiYyc3kfoKsqhn2zJWsMzqOZ3-Z3OYoORcJC9mJtpt=Ogm3Vg@mail.gmail.com>
Richard,
On 18.03.21 13:35, Richard Biener via Fortran wrote:
> [...]
> Since the libgfortran MATMUL should be vectorized
> I think it's not reasonable to inline any but _very_ small
> MATMUL at optimization levels that do not enable vectorization.
Besides the obvious if (!flag_external_blas) which should always prevent
inlining (possibly except for tiny N like N=1), your idea is 'if (N
small || flag_tree_loop_vectorize)'?
Or are you thinking of a different or additional flag_... than
flag_tree_loop_vectorize for making this choice?
Tobias
-----------------
Mentor Graphics (Deutschland) GmbH, Arnulfstrasse 201, 80634 München Registergericht München HRB 106955, Geschäftsführer: Thomas Heurung, Frank Thürauf
next prev parent reply other threads:[~2021-03-18 14:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 7:48 Steve Kargl
2021-03-18 12:35 ` Richard Biener
2021-03-18 14:48 ` Tobias Burnus [this message]
2021-03-18 15:05 ` Richard Biener
2021-03-18 16:13 ` Steve Kargl
2021-03-18 18:16 ` Thomas Koenig
2021-03-18 18:24 ` Thomas Koenig
2021-03-18 20:22 ` Steve Kargl
2021-03-18 20:55 ` Thomas Koenig
2021-03-18 22:07 ` Steve Kargl
2021-03-19 6:19 ` Thomas Koenig
2021-03-19 6:36 ` Thomas Koenig
2021-03-19 19:12 ` Steve Kargl
2021-03-19 7:03 ` Steve Kargl
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=563cee48-fbcc-09bc-0cd1-f05082e4feb3@codesourcery.com \
--to=tobias@codesourcery.com \
--cc=fortran@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
--cc=sgk@troutmask.apl.washington.edu \
--cc=tkoenig@netcologne.de \
/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).