public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bernd Schmidt <bernds@codesourcery.com>
To: Eric Botcazou <ebotcazou@adacore.com>, <gcc-patches@gcc.gnu.org>
Cc: Sebastien Bourdeauducq <sebastien@milkymist.org>,
	Anthony Green	<green@moxielogic.com>,
	Chung-Lin Tang <cltang@codesourcery.com>,
	Sandra Loosemore <sandra@codesourcery.com>,
	DJ Delorie <dj@redhat.com>, Nick Clifton	<nickc@redhat.com>
Subject: Re: Housekeeping work in backends.html
Date: Sat, 10 Jan 2015 00:46:00 -0000	[thread overview]
Message-ID: <54B06BBA.4000105@codesourcery.com> (raw)
In-Reply-To: <4514618.3Cs2Dcpn5F@polaris>

On 01/07/2015 12:39 AM, Eric Botcazou wrote:
>> Some ports are missing (lm32, moxie, nios2, nvptx, rl78, rx) so the relevant
>> maintainers are CCed (see 6.3.9 Anatomy of a Target Back End in the doc).
>
> The page is directly browsable at https://gcc.gnu.org/backends.html
>
> For the moxie, nvptx, rl178 and rx ports, maintainers can send me the string
> as Sandra did for the nios2 port and I'll update the document.

For nvptx it's not really clear what to use in some cases, and in others 
I have no idea why we would need to keep track of these "characteristics".

H - you could argue a hardware implementation does not exist as it's a
     virtual target, but it can obviously be compiled down to run on
     hardware that does exist.
Q - "registers" are typed and you can declare 64 bit registers, so
     probably this is true
f - Not even sure what this is about. It only defines a small epilogue
     pattern.
a - Port uses neither LRA nor reload. Might be a new characteristic
     (along with several others).

The closest string is probably

SQCqfbde


Bernd

  parent reply	other threads:[~2015-01-10  0:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-05 23:20 Eric Botcazou
2015-01-06 18:43 ` Jeff Law
2015-01-06 23:04   ` Eric Botcazou
2015-01-06 20:50 ` Sandra Loosemore
2015-01-06 23:16   ` Eric Botcazou
2015-01-06 23:41 ` Eric Botcazou
2015-01-07  0:10   ` Max Filippov
2015-01-07  8:11     ` Eric Botcazou
2015-01-10  0:46   ` Bernd Schmidt [this message]
2015-01-13 23:25     ` Eric Botcazou
2015-01-20  9:27   ` Eric Botcazou
2015-01-07  8:44 ` Eric Botcazou
2015-01-20 13:25   ` Steven Bosscher
2015-01-20 18:45     ` Eric Botcazou
2015-01-21  9:27     ` Eric Botcazou
2015-01-07  9:28 ` Eric Botcazou
2015-01-14  3:55 ` Anthony Green
2015-01-14  9:46   ` Eric Botcazou
2015-01-20 10:59 ` Eric Botcazou

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=54B06BBA.4000105@codesourcery.com \
    --to=bernds@codesourcery.com \
    --cc=cltang@codesourcery.com \
    --cc=dj@redhat.com \
    --cc=ebotcazou@adacore.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=green@moxielogic.com \
    --cc=nickc@redhat.com \
    --cc=sandra@codesourcery.com \
    --cc=sebastien@milkymist.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).