public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Chris Metcalf <cmetcalf@ezchip.com>
To: Chen Gang S <gang.chen@sunrus.com.cn>, <walt@tilera.com>
Cc: Jeff Law <law@redhat.com>, gcc-help <gcc-help@gcc.gnu.org>,
	Mike Stump	<mikestump@comcast.net>
Subject: Re: [Consult] tile: How to construct testsuite for tile architecture without hardware.
Date: Mon, 19 Jan 2015 16:10:00 -0000	[thread overview]
Message-ID: <54BD2C5E.1070804@ezchip.com> (raw)
In-Reply-To: <54BA30F3.4080202@sunrus.com.cn>

On 1/17/2015 4:52 AM, Chen Gang S wrote:
> Hello Maintainers:
>
> I am trying to make gcc patches for tile, and need testsuite without
> related hardware, so I consult:

Unfortunately, at the current time, the simulator is only available as part of the commercial Multicore Development Environment package.  A qemu port for tile hardware would certainly be welcome, but to my knowledge, no one has completed such a port yet.  ISA and ABI documentation for tilegx are available at www.tilera.com/scm.

-- 
Chris Metcalf, EZChip Semiconductor
http://www.ezchip.com

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

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-17  9:45 Chen Gang S
2015-01-17 17:04 ` Mike Stump
2015-01-17 23:32   ` Chen Gang S
2015-01-19 16:10 ` Chris Metcalf [this message]
2015-01-20  1:54   ` Chen Gang S
2015-01-24 13:24     ` Chen Gang S
2015-01-30 22:50       ` Chen Gang S
2015-01-30 23:01         ` Mike Stump
2015-01-31  5:45           ` Chen Gang S
2015-01-31 11:17             ` Chen Gang S
2015-01-31 19:44               ` Mike Stump
2015-02-01  0:20                 ` Chen Gang S
2015-02-03 14:20                 ` Chen Gang S
2015-02-03 14:28                   ` Chen Gang S
2015-02-03 17:24                   ` Mike Stump
2015-02-03 23:00                     ` Chen Gang S
2015-07-19 22:25       ` Chen Gang
2015-07-29 21:00         ` Chen Gang
     [not found]           ` <55E27DB9.6050606@hotmail.com>
2015-08-30  3:50             ` Chen Gang
2015-10-01  4:10               ` Chen Gang
     [not found]               ` <560CB2C0.7000107@hotmail.com>
2015-10-04 11:55                 ` Chen Gang
2015-10-05 11:59                   ` Chen Gang
2015-10-17  6:37                     ` Chen Gang
2015-10-18  5:22                       ` Chen Gang
2015-10-18  5:42                         ` john.frankish
2015-10-19 18:27                         ` Mike Stump
     [not found]                           ` <562572E2.6020308@hotmail.com>
2015-10-19 22:45                             ` Chen Gang
2015-10-21 16:40                               ` Mike Stump
     [not found]                                 ` <5628110A.90701@hotmail.com>
2015-10-21 22:25                                   ` Chen Gang
     [not found]                       ` <56232CE1.6050405@hotmail.com>
2015-11-30 13:55                         ` Chen Gang
     [not found]                         ` <565C55D3.1060608@hotmail.com>
2016-03-06  0:06                           ` Chen Gang
2016-03-13 10:34                             ` Chen Gang
2016-05-29  7:36                               ` Chen Gang

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=54BD2C5E.1070804@ezchip.com \
    --to=cmetcalf@ezchip.com \
    --cc=gang.chen@sunrus.com.cn \
    --cc=gcc-help@gcc.gnu.org \
    --cc=law@redhat.com \
    --cc=mikestump@comcast.net \
    --cc=walt@tilera.com \
    /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).