From: Dan Kegel <dank@kegel.com>
To: "Stewart, Richard" <rstewart@mc.com>
Cc: gdb@sources.redhat.com
Subject: Re: GDB 4.18 with GCC 3.3.6
Date: Fri, 08 Jul 2005 13:42:00 -0000 [thread overview]
Message-ID: <42CE80AA.7040508@kegel.com> (raw)
In-Reply-To: <190C93606B0ADD40B7968DAFAA3E192867EB0E@ad-email1.ad.mc.com>
Stewart, Richard wrote:
> I would like to use GDB 4.18 with GCC 3.3.6 and possibly even newer
> versions of GCC. I'm using GCC 2.95 right now and would like to gain
> some of the performance improvements in the newer versions of the
> compiler
Um, better be sure there really are performance improvements
before you dive in. One app that I care about runs slower
on gcc-3.4.1 than on gcc-2.95.3.
I'm putting together a performance regression benchmark
suite right now by pulling together all the known microbenchmarks
that run slower on newer versions of gcc, in hopes
of helping make sure that gcc-4.1 resolves most of them.
- Dan
--
Trying to get a job as a c++ developer? See http://kegel.com/academy/getting-hired.html
next prev parent reply other threads:[~2005-07-08 13:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-08 12:08 Stewart, Richard
2005-07-08 13:42 ` Dan Kegel [this message]
2005-07-08 14:33 ` Matthew J Fletcher
2005-07-08 14:50 ` Dan Kegel
2005-07-08 13:56 ` Daniel Jacobowitz
2005-07-08 19:02 ` Jason Molenda
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=42CE80AA.7040508@kegel.com \
--to=dank@kegel.com \
--cc=gdb@sources.redhat.com \
--cc=rstewart@mc.com \
/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