public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Benjamin Kosnik <bkoz@redhat.com>
To: gcc@gcc.gnu.org
Cc: viktor.przebinda@colorado.edu
Subject: Re: optimization
Date: Tue, 09 Dec 2003 18:18:00 -0000	[thread overview]
Message-ID: <20031209120753.1b2fce7e.bkoz@redhat.com> (raw)

> optimization that would have its greatest impact on scientific code written in C++. 

Do you have any specifics? I imagine it would be pretty easy to find
interest for this project. I'd suggest that you come up with a detailed
proposal and post it on this list for comment. You may be interested in
the tree-SSA infrastructure, see:
http://gcc.gnu.org/projects/tree-ssa/

However, if you are just looking for suggestions, there are a number of
C++ scientific libraries that would be interested in increasing
performance, some of which are listed below.

- ginac (symbolic algebra)
  http://www.ginac.de/
- pooma (parallel scientific computation)
  http://www.codesourcery.com/pooma/pooma
- goose (stats)
  http://www.gnu.org/software/goose/goose.html
- itk (algo parts)
  http://www.itk.org

A first step might be doing performance analysis of these libraries,
finding bottlenecks, and then working to resolve these deficiencies.

There are, or have been, issues with performance of C++'s complex type.
Perhaps Joe Buck could give more information on this.

There are people on this list (or gcc developers) that seem to be
interested in this subject. Off the top of my head, these people include
Roger Sayle, Scott Synder, Scott Robert Ladd, Gabriel Dos Reis, etc. I'm
sure there are others.

good luck,
-benjamin

             reply	other threads:[~2003-12-09 18:09 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-09 18:18 Benjamin Kosnik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-12-09 16:42 optimization Viktor Przebinda
2003-12-09 17:29 ` optimization Diego Novillo
2003-12-09 18:53 ` optimization Scott Robert Ladd
2003-05-02 12:05 Optimization Piotr Wyderski
2003-05-02 23:08 ` Optimization Richard Henderson
2003-05-03  0:12   ` Optimization Andrew Pinski
2003-05-03  1:14     ` Optimization Richard Henderson
2000-05-11 11:21 Optimization Thomas, Robert S
2000-05-11 11:31 ` Optimization Jeffrey A Law
1999-03-30  5:07 Optimization Oskar Enoksson
1999-03-31 23:46 ` Optimization Oskar Enoksson
1998-03-29  5:14 Optimization Oskar Enoksson
1998-04-02  3:41 ` Optimization John Carr
1998-04-02  8:21 ` Optimization Jeffrey A Law
1998-04-02 11:32 ` Optimization Jim Wilson
1998-04-02  3:41   ` Optimization Oskar Enoksson
1998-04-03 21:52     ` Optimization John Carr
1998-04-02 11:32 ` Optimization Joern Rennecke
1999-03-29  8:18 ` Optimization Jeffrey A Law
1999-03-31 23:46   ` Optimization Jeffrey A Law

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=20031209120753.1b2fce7e.bkoz@redhat.com \
    --to=bkoz@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=viktor.przebinda@colorado.edu \
    /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).