From: Oleg Endo <oleg.endo@t-online.de>
To: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: [wwwdocs] SH - add 'b' target characteristic
Date: Sun, 15 Jul 2012 22:57:00 -0000 [thread overview]
Message-ID: <1342393021.2244.17.camel@yam-132-YW-E178-FTW> (raw)
Hello,
If I'm not mistaken, the SH target does not use the '"* ..."' notation
for output template code. The patch below updates the table in
backends.html to reflect the current status.
Cheers,
Oleg
Index: htdocs/backends.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/backends.html,v
retrieving revision 1.45
diff -u -r1.45 backends.html
--- htdocs/backends.html 23 Feb 2012 13:24:36 -0000 1.45
+++ htdocs/backends.html 15 Jul 2012 22:52:00 -0000
@@ -96,7 +96,7 @@
pdp11 | L IC qrcp e
rs6000 | Q C qr da
s390 | ? Q qr p g bda e
-sh | Q CB qr da
+sh | Q CB qr bda
sparc | Q CB qr p da
spu | ? Q *C p g bd
stormy16 | ???L FIC D l p m a
next reply other threads:[~2012-07-15 22:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-15 22:57 Oleg Endo [this message]
2012-07-16 0:24 ` Kaz Kojima
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=1342393021.2244.17.camel@yam-132-YW-E178-FTW \
--to=oleg.endo@t-online.de \
--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).