From: lsjoberg@aland.net (Linus Sjöberg)
To: gcc@gcc.gnu.org
Subject: Re: Readiness of tree-ssa
Date: Thu, 05 Feb 2004 18:59:00 -0000 [thread overview]
Message-ID: <86znbx73pm.fsf@clarke.alcom.aland.fi> (raw)
In-Reply-To: <Pine.LNX.4.44.0402041646080.26022-100000@gandalf.ices.utexas.edu>
Wolfgang Bangerth <bangerth@ices.utexas.edu> writes:
> 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++ :-)
I did the same with a research project I am involved in which contains something
like 50.000 lines of C++ and a whole bunch of not-so-nice constructs. With the
latest tree-ssa it compiles nicely (We actually found a bunch of bugs in our
code due to the new parser!) and all test-cases pass.
/LS
next prev parent reply other threads:[~2004-02-05 18:59 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
2004-02-05 18:59 ` Linus Sjöberg [this message]
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=86znbx73pm.fsf@clarke.alcom.aland.fi \
--to=lsjoberg@aland.net \
--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).