public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Jeff Law <law@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. f29b024ac47d14e19c62ad5911708b37455b5706
Date: Wed,  7 Jun 2023 21:26:33 +0000 (GMT)	[thread overview]
Message-ID: <20230607212633.906703858C1F@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  f29b024ac47d14e19c62ad5911708b37455b5706 (commit)
      from  92f8ddac1b1e08cb648b812d0dccce9c27f15206 (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 f29b024ac47d14e19c62ad5911708b37455b5706
Author: Jeff Law <jlaw@ventanamicro.com>
Date:   Wed Jun 7 15:26:14 2023 -0600

    Update LRA status for various ports that have been recently converted.

diff --git a/htdocs/backends.html b/htdocs/backends.html
index 361c4b49..bdaf29ad 100644
--- a/htdocs/backends.html
+++ b/htdocs/backends.html
@@ -76,25 +76,25 @@ avr        |    L  FI    l  p   g
 bfin       |       F            gi
 c6x        |   S     CB         gi
 cr16       |    L  F C          g    s
-cris       |       F  B         gi   s
+cris       |       F  B         gia  s
 csky       |                 b   ia
-epiphany   |         C          gi   s
+epiphany   |         C          gia  s
 fr30       | ??    FI B     pb mg    s
 frv        | ??       B      b   i   s
 gcn        |   S     C D  q       a e
-h8300      |       FI B         g    s
+h8300      |       FI B         g a  s
 i386       |     Q        q  b   ia
 ia64       |   ? Q   C    qr b m i
-iq2000     | ???   FICB      b  g  t
+iq2000     | ???   FICB      b  g at
 lm32       |       F            g
 m32c       |    L  FI    l   b  g    s
-m32r       |       FI        b       s
+m32r       |       FI        b    a  s
 m68k       |                pb   i
 mcore      |  ?    FI       pb mg    s
 mep        |       F C       b  g  t s
-microblaze |         CB          i   s
+microblaze |         CB          ia  s
 mips       |     Q   CB   qr     ia  s
-mmix       | HM  Q   C    q      i  e
+mmix       | HM  Q   C    q      ia e
 mn10300    | ??                 gi   s
 moxie      |       F            g  t s
 msp430     |    L  FI    l   b  g    s
@@ -111,7 +111,7 @@ rx         |                         s
 s390       |     Q        qr    gia e
 sh         |     Q   CB   qrp    i
 sparc      |     Q   CB   qr b   ia
-stormy16   | ???L  FIC D l   b   i
+stormy16   | ???L  FIC D l   b   ia
 tilegx     |     Q   C    q     gi  e
 tilepro    |   S   F C          gi  e
 v850       |                    g a  s

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

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


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2023-06-07 21:26 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=20230607212633.906703858C1F@sourceware.org \
    --to=law@sourceware.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).