public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: segher@gcc.gnu.org
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 77d900eae547f79868f34f5879ebaacf9c6cf07d
Date: Fri, 29 Nov 2019 17:22:00 -0000	[thread overview]
Message-ID: <20191129172220.63854.qmail@sourceware.org> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gcc-wwwdocs".

The branch, master has been updated
       via  77d900eae547f79868f34f5879ebaacf9c6cf07d (commit)
      from  553b5e98de2dc90183773b0c0d750db62d6ad8db (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 77d900eae547f79868f34f5879ebaacf9c6cf07d
Author: Segher Boessenkool <segher@kernel.crashing.org>
Date:   Fri Nov 29 17:15:24 2019 +0000

    Update simulator in backends.html (i386, m68k, s390, tilegx)
    
    All of i386, m68k, s390, and tilegx are supported in QEMU (see
    https://wiki.qemu.org/Documentation/Platforms for example), so they
    should not have "S" (or "?" in that column).

diff --git a/htdocs/backends.html b/htdocs/backends.html
index a392d5e..2de21fe 100644
--- a/htdocs/backends.html
+++ b/htdocs/backends.html
@@ -84,13 +84,13 @@ fr30       | ??    FI B      pb mg    s
 frv        | ??       B       b   i   s
 gcn        |   S     C D  q        a e
 h8300      |       FI B     c    g    s
-i386       |   ? Q        q   b   ia
+i386       |     Q        q   b   ia
 ia64       |   ? Q   C    qr  b m i
 iq2000     | ???   FICB       b  g  t
 lm32       |       F             g
 m32c       |    L  FI    l    b  g    s
 m32r       |       FI         b       s
-m68k       |   ?             pb   i
+m68k       |                 pb   i
 mcore      |  ?    FI        pb mg    s
 mep        |       F C        b  g  t s
 microblaze |         CB           i   s
@@ -110,11 +110,11 @@ riscv      |     Q   C    qr     gia
 rl78       |    L  F     l       g    s
 rs6000     |     Q   C    qr pb   ia
 rx         |                          s
-s390       |   ? Q        qr     gia e
+s390       |     Q        qr     gia e
 sh         |     Q   CB   qr p    i
 sparc      |     Q   CB   qr  b   ia
 stormy16   | ???L  FIC D l    b   i
-tilegx     |   S Q   C    q      gi  e
+tilegx     |     Q   C    q      gi  e
 tilepro    |   S   F C           gi  e
 v850       |                     g a  s
 vax        |  M     I       c b   i  e

-----------------------------------------------------------------------

Summary of changes:
 htdocs/backends.html |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2019-11-29 17:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20191129172220.63854.qmail@sourceware.org \
    --to=segher@gcc.gnu.org \
    --cc=gcc-cvs-wwwdocs@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).