From: "Tom G. Christensen" <tgc@jupiterrise.com>
To: gcc-patches@gcc.gnu.org
Subject: [wwwdocs] Buildstat update for 5.1
Date: Mon, 01 Jun 2015 19:41:00 -0000 [thread overview]
Message-ID: <20150601194044.GC7781@odin.tgcnet> (raw)
[-- Attachment #1: Type: text/plain, Size: 314 bytes --]
Latest results for 5.1.x
-tgc
Testresults for 5.1.0:
arm-unknown-linux-gnueabi
hppa-unknown-linux-gnu
hppa1.1-hp-hpux10.20
hppa2.0w-hp-hpux11.00
i686-unknown-linux-gnu
mips-unknown-linux-gnu
mipsel-unknown-linux-gnu
powerpc-unknown-linux-gnu
sparc-unknown-linux-gnu
x86_64-unknown-linux-gnu
[-- Attachment #2: buildstat-5.1.patch --]
[-- Type: text/plain, Size: 2436 bytes --]
Index: buildstat.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-5/buildstat.html,v
retrieving revision 1.2
diff -u -r1.2 buildstat.html
--- buildstat.html 29 May 2015 14:05:08 -0000 1.2
+++ buildstat.html 1 Jun 2015 19:26:08 -0000
@@ -31,6 +31,38 @@
</tr>
<tr>
+<td>arm-unknown-linux-gnueabi</td>
+<td> </td>
+<td>Test results:
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2015-05/msg00965.html">5.1.0</a>
+</td>
+</tr>
+
+<tr>
+<td>hppa-unknown-linux-gnu</td>
+<td> </td>
+<td>Test results:
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2015-05/msg00763.html">5.1.0</a>
+</td>
+</tr>
+
+<tr>
+<td>hppa1.1-hp-hpux10.20</td>
+<td> </td>
+<td>Test results:
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2015-05/msg01852.html">5.1.0</a>
+</td>
+</tr>
+
+<tr>
+<td>hppa2.0w-hp-hpux11.00</td>
+<td> </td>
+<td>Test results:
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2015-05/msg01517.html">5.1.0</a>
+</td>
+</tr>
+
+<tr>
<td>i386-pc-solaris2.12</td>
<td> </td>
<td>Test results:
@@ -39,6 +71,38 @@
</tr>
<tr>
+<td>i686-unknown-linux-gnu</td>
+<td> </td>
+<td>Test results:
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2015-05/msg00687.html">5.1.0</a>
+</td>
+</tr>
+
+<tr>
+<td>mips-unknown-linux-gnu</td>
+<td> </td>
+<td>Test results:
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2015-05/msg01101.html">5.1.0</a>
+</td>
+</tr>
+
+<tr>
+<td>mipsel-unknown-linux-gnu</td>
+<td> </td>
+<td>Test results:
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2015-05/msg01480.html">5.1.0</a>
+</td>
+</tr>
+
+<tr>
+<td>powerpc-unknown-linux-gnu</td>
+<td> </td>
+<td>Test results:
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2015-05/msg01751.html">5.1.0</a>
+</td>
+</tr>
+
+<tr>
<td>sparc-sun-solaris2.11</td>
<td> </td>
<td>Test results:
@@ -47,6 +111,14 @@
</tr>
<tr>
+<td>sparc-unknown-linux-gnu</td>
+<td> </td>
+<td>Test results:
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2015-05/msg00966.html">5.1.0</a>
+</td>
+</tr>
+
+<tr>
<td>x86_64-apple-darwin11.4.2</td>
<td> </td>
<td>Test results:
@@ -66,6 +138,7 @@
<td>x86_64-unknown-linux-gnu</td>
<td> </td>
<td>Test results:
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2015-05/msg00567.html">5.1.0</a>,
<a href="https://gcc.gnu.org/ml/gcc-testresults/2015-05/msg00005.html">5.1.0</a>
</td>
</tr>
next reply other threads:[~2015-06-01 19:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 19:41 Tom G. Christensen [this message]
2015-06-02 13:30 ` Gerald Pfeifer
-- strict thread matches above, loose matches on Subject: below --
2015-05-03 15:28 Tom G. Christensen
2015-05-29 14:14 ` Gerald Pfeifer
2015-06-01 19:42 ` Tom G. Christensen
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=20150601194044.GC7781@odin.tgcnet \
--to=tgc@jupiterrise.com \
--cc=gcc-patches@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).