From: Aldy Hernandez <aldyh@redhat.com>
To: gcc external <gcc@gcc.gnu.org>
Subject: Re: 51 GCC regressions, 0 new, with your patch on 2001-12-15T06:07:31Z.
Date: Sat, 15 Dec 2001 18:35:00 -0000 [thread overview]
Message-ID: <1008467952.21803.322.camel@litecycle.cc.andrews.edu> (raw)
In-Reply-To: <200112150859.fBF8xBZ08873@maat.cygnus.com>
it seems every few days the regressions increase. what's going on? are
people not fixing their regressions?
On Sat, 2001-12-15 at 00:59, GCC regression checker wrote:
> With your recent patch, GCC has some regression test failures, which
> used to pass. There are 0 new failures, and 51
> failures that existed before and after that patch; 0 failures
> have been fixed.
>
> The old failures, which were not fixed or introduced by your patch, are:
> powerpc-eabisim g++.sum g++.ext/instantiate2.C
> powerpc-eabisim g++.sum g++.ext/instantiate3.C
> powerpc-eabisim g++.sum g++.other/init15.C
> powerpc-eabisim gcc.sum gcc.c-torture/execute/20000808-1.c
> powerpc-eabisim gcc.sum gcc.c-torture/execute/20010123-1.c
> powerpc-eabisim gcc.sum gcc.c-torture/execute/920428-2.c
> powerpc-eabisim gcc.sum gcc.c-torture/execute/920501-3.c
> powerpc-eabisim gcc.sum gcc.c-torture/execute/920501-7.c
> powerpc-eabisim gcc.sum gcc.c-torture/execute/950607-2.c
> powerpc-eabisim gcc.sum gcc.c-torture/execute/comp-goto-2.c
> powerpc-eabisim gdb.sum gdb.base/a2-run.exp:
> powerpc-eabisim gdb.sum gdb.base/break.exp:
> powerpc-eabisim gdb.sum gdb.base/condbreak.exp:
> powerpc-eabisim gdb.sum gdb.base/dbx.exp:
> powerpc-eabisim gdb.sum gdb.base/define.exp:
> powerpc-eabisim gdb.sum gdb.base/display.exp:
> powerpc-eabisim gdb.sum gdb.base/ena-dis-br.exp:
> powerpc-eabisim gdb.sum gdb.base/ending-run.exp:
> powerpc-eabisim gdb.sum gdb.base/funcargs.exp:
> powerpc-eabisim gdb.sum gdb.base/interrupt.exp:
> powerpc-eabisim gdb.sum gdb.base/list.exp:
> powerpc-eabisim gdb.sum gdb.base/maint.exp:
> powerpc-eabisim gdb.sum gdb.base/printcmds.exp:
> powerpc-eabisim gdb.sum gdb.base/ptype.exp:
> powerpc-eabisim gdb.sum gdb.base/remote.exp:
> powerpc-eabisim gdb.sum gdb.base/reread.exp:
> powerpc-eabisim gdb.sum gdb.base/scope.exp:
> powerpc-eabisim gdb.sum gdb.base/setshow.exp:
> powerpc-eabisim gdb.sum gdb.base/whatis.exp:
> powerpc-eabisim gdb.sum gdb.c++/anon-union.exp:
> powerpc-eabisim gdb.sum gdb.c++/misc.exp:
> native g++.sum g++.abi/cxa_vec.C
> native g++.sum g++.dg/eh/omit-frame-pointer.C
> native g++.sum g++.dg/eh/registers1.C
> native g++.sum g++.eh/badalloc1.C
> native g++.sum g++.eh/fntry1.C
> native g++.sum g++.eh/rethrow1.C
> native g++.sum g++.eh/rethrow2.C
> native g++.sum g++.eh/rethrow3.C
> native g++.sum g++.eh/rethrow6.C
> native g++.sum g++.eh/spec2.C
> native g++.sum g++.mike/eh23.C
> native g++.sum g++.mike/eh33.C
> native g++.sum g++.mike/eh39.C
> native g++.sum g++.mike/eh40.C
> native g++.sum g++.mike/eh50.C
> native g++.sum g++.mike/eh51.C
> native gcc.sum gcc.c-torture/execute/920428-2.c
> native gcc.sum gcc.c-torture/execute/920501-3.c
> native gcc.sum gcc.c-torture/execute/920501-7.c
> native gcc.sum gcc.c-torture/execute/comp-goto-2.c
>
> For more information, see <http://people.redhat.com/geoffk/gcc-regression/>.
parent reply other threads:[~2001-12-16 1:57 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200112150859.fBF8xBZ08873@maat.cygnus.com>]
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=1008467952.21803.322.camel@litecycle.cc.andrews.edu \
--to=aldyh@redhat.com \
--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).