public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joe Buck <Joe.Buck@synopsys.COM>
To: Wolfgang Bangerth <bangerth@ices.utexas.edu>
Cc: gcc@gcc.gnu.org, gerald@pfeifer.com
Subject: Re: Readiness of tree-ssa
Date: Thu, 05 Feb 2004 00:06:00 -0000	[thread overview]
Message-ID: <20040204160624.A19892@synopsys.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0402041646080.26022-100000@gandalf.ices.utexas.edu>; from bangerth@ices.utexas.edu on Wed, Feb 04, 2004 at 04:50:26PM -0600

On Wed, Feb 04, 2004 at 04:50:26PM -0600, Wolfgang Bangerth wrote:
> I had promised to run tree-ssa against our application (deal.II) and our 
> testsuite. The results are great: not a single one of the 200+ testcases 
> fails, and none of those applications build on top of the library that I 
> tested gave different results either. So there are at least no obvious 
> miscompilations any more in my 200,000+ lines of C++ :-)

Cool.  Has anyone built KDE with tree-ssa recently?

  parent reply	other threads:[~2004-02-05  0:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-04 22:50 Wolfgang Bangerth
2004-02-04 22:53 ` Richard Guenther
2004-02-05  0:06 ` Joe Buck [this message]
2004-02-05 18:59 ` Linus Sjöberg
2004-02-09 16:31 ` Gerald Pfeifer
  -- strict thread matches above, loose matches on Subject: below --
2004-01-20 19:48 Wolfgang Bangerth
2004-01-20 20:00 ` Richard Guenther
2004-01-20 20:07   ` Diego Novillo
2004-01-20 21:55     ` Richard Guenther
2004-01-21 19:44 ` Diego Novillo
2004-01-21 20:38   ` Wolfgang Bangerth
2004-01-21 20:46     ` Diego Novillo
2004-01-21 20:50       ` Wolfgang Bangerth
2004-01-21 20:52         ` Diego Novillo
2004-01-21 20:59         ` Paul Jarc
2004-01-21 21:13       ` Daniel Berlin
2004-01-21 21:30         ` Gabriel Dos Reis
2004-01-21 21:31           ` Wolfgang Bangerth
2004-01-21 21:38           ` Daniel Berlin
2004-01-22 17:27     ` Wolfgang Bangerth
2004-01-23 14:37     ` Gerald Pfeifer
2004-01-23 17:01       ` Wolfgang Bangerth

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=20040204160624.A19892@synopsys.com \
    --to=joe.buck@synopsys.com \
    --cc=bangerth@ices.utexas.edu \
    --cc=gcc@gcc.gnu.org \
    --cc=gerald@pfeifer.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).