public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/51119] MATMUL slow for large matrices
Date: Fri, 29 Jun 2012 10:56:00 -0000	[thread overview]
Message-ID: <bug-51119-4-RGw6j3HKAj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51119-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51119

Steven Bosscher <steven at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |steven at gcc dot gnu.org

--- Comment #9 from Steven Bosscher <steven at gcc dot gnu.org> 2012-06-29 10:55:48 UTC ---
(In reply to comment #7)
> IIRC I reached about 30-40 % of peak
> flops which was a bit disappointing.

This sounds quite impressive to me, actually.

It would be interesting to investigate using the IFUNC mechanism to provide
optimized (e.g. vectorized) versions of some of the library functions.


  parent reply	other threads:[~2012-06-29 10:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-14  8:16 [Bug libfortran/51119] New: " jb at gcc dot gnu.org
2011-11-14  8:17 ` [Bug libfortran/51119] " jb at gcc dot gnu.org
2011-11-14 13:56 ` burnus at gcc dot gnu.org
2011-11-15 12:35 ` Joost.VandeVondele at mat dot ethz.ch
2011-11-15 12:37 ` Joost.VandeVondele at mat dot ethz.ch
2011-11-15 16:19 ` jb at gcc dot gnu.org
2012-06-28 11:58 ` Joost.VandeVondele at mat dot ethz.ch
2012-06-28 12:15 ` jb at gcc dot gnu.org
2012-06-29  7:19 ` Joost.VandeVondele at mat dot ethz.ch
2012-06-29 10:56 ` steven at gcc dot gnu.org [this message]
2013-03-29  8:47 ` Joost.VandeVondele at mat dot ethz.ch
2013-04-01 15:59 ` tkoenig at gcc dot gnu.org
2015-10-31 14:15 ` dominiq at lps dot ens.fr

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-51119-4-RGw6j3HKAj@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).