From: Viktor Przebinda <viktor.przebinda@colorado.edu>
To: gcc@gcc.gnu.org
Subject: optimization
Date: Tue, 09 Dec 2003 16:42:00 -0000 [thread overview]
Message-ID: <CDA4745A-2A64-11D8-ACD2-000393B6616A@colorado.edu> (raw)
I am interested in doing a long term (1.5 years) project with g++
related to optimization for a masters thesis in computer engineering.
More specifically, optimization that would have its greatest impact on
scientific code written in C++. Target platform could be either PowerPC
or x86. I have already looked at gcc's website on the subject of
optimization deficiencies without much luck. These projects either
seemed too small or not related to scientific computing applications.
If anyone has some ideas please let me know.
Viktor
viktor.przebinda@colorado.edu
next reply other threads:[~2003-12-09 16:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-09 16:42 Viktor Przebinda [this message]
2003-12-09 17:29 ` optimization Diego Novillo
2003-12-09 18:53 ` optimization Scott Robert Ladd
-- strict thread matches above, loose matches on Subject: below --
2003-12-09 18:18 optimization Benjamin Kosnik
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=CDA4745A-2A64-11D8-ACD2-000393B6616A@colorado.edu \
--to=viktor.przebinda@colorado.edu \
--cc=gcc@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).