public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "christian dot joensson at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug treelang/23072] multiple runs of treelang testsuite does not work...
Date: Sat, 13 Aug 2005 07:42:00 -0000	[thread overview]
Message-ID: <20050813074157.29192.qmail@sourceware.org> (raw)
In-Reply-To: <20050726092222.23072.christian.joensson@gmail.com>


------- Additional Comments From christian dot joensson at gmail dot com  2005-08-13 07:41 -------
So, this is what it looks like now:

Test Run By chj on Sat Aug 13 09:36:47 2005
Native configuration is sparc64-unknown-linux-gnu

                === treelang tests ===

Schedule of variations:
    unix/-m64
    unix

Running target unix/-m64
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using /usr/local/src/branch/gcc/gcc/testsuite/config/default.exp as
tool-and-target-specific interface file.
Running /usr/local/src/branch/gcc/gcc/testsuite/treelang/compile/compile.exp ...
Running /usr/local/src/branch/gcc/gcc/testsuite/treelang/execute/execute.exp ...
Running /usr/local/src/branch/gcc/gcc/testsuite/treelang/output/output.exp ...

                === treelang Summary for unix/-m64 ===

# of expected passes            48
Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using /usr/local/src/branch/gcc/gcc/testsuite/config/default.exp as
tool-and-target-specific interface file.
Running /usr/local/src/branch/gcc/gcc/testsuite/treelang/compile/compile.exp ...
Running /usr/local/src/branch/gcc/gcc/testsuite/treelang/execute/execute.exp ...
Running /usr/local/src/branch/gcc/gcc/testsuite/treelang/output/output.exp ...

                === treelang Summary for unix ===

# of expected passes            48

                === treelang Summary ===

# of expected passes            96

This is with http://gcc.gnu.org/ml/gcc-patches/2005-08/msg00661.html (and the
rest of removal and addition of files from your mainline patch here:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23072#c7)

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23072


  parent reply	other threads:[~2005-08-13  7:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-26  9:36 [Bug treelang/23072] New: " christian dot joensson at gmail dot com
2005-07-27 12:26 ` [Bug treelang/23072] " christian dot joensson at gmail dot com
2005-08-05 12:22 ` christian dot joensson at gmail dot com
2005-08-05 12:23 ` christian dot joensson at gmail dot com
2005-08-05 14:47 ` phython at gcc dot gnu dot org
2005-08-05 15:01 ` christian dot joensson at gmail dot com
2005-08-05 17:27 ` phython at gcc dot gnu dot org
2005-08-06 18:25 ` cvs-commit at gcc dot gnu dot org
2005-08-06 18:56 ` phython at gcc dot gnu dot org
2005-08-07  5:14 ` christian dot joensson at gmail dot com
2005-08-07  5:19 ` christian dot joensson at gmail dot com
2005-08-07  5:50 ` phython at gcc dot gnu dot org
2005-08-10  7:48 ` christian dot joensson at gmail dot com
2005-08-13  7:42 ` christian dot joensson at gmail dot com [this message]
2005-08-13 16:32 ` phython at gcc dot gnu dot org
     [not found] <bug-23072-3388@http.gcc.gnu.org/bugzilla/>
2005-11-06 16:51 ` phython at gcc dot gnu dot org

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=20050813074157.29192.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).