public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Walter Lee <walt@tilera.com>
To: <binutils@sourceware.org>
Subject: Re: new port for TILEPro and TILE-Gx processors (ld files)
Date: Fri, 10 Jun 2011 06:37:00 -0000	[thread overview]
Message-ID: <4DF1BB8B.2040402@tilera.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1106062010100.18407@digraph.polyomino.org.uk>

[-- Attachment #1: Type: text/plain, Size: 936 bytes --]

Here is a resubmission of the ld files, without forking elf.sc.

2011-06-10  Walter Lee  <walt@tilera.com>

	* Makefile.am (ALL_EMULATION_SOURCES): Add eelf32tilegx.c and
	eelf32tilepro.c.
	(ALL_64_EMULATION_SOURCES): Add eelf64tilegx.c.
	(eelf32tilegx.c): New target.
	(eelf32tilepro.c): Likewise.
	(eelf64tilegx.c): Likewise.
	* Makefile.in: Regenerate.
	* configure.tgt: Handle tilegx-*-* and tilepro-*-*.
	* emulparams/elf32tilegx.sh: New file.
	* emulparams/elf64tilegx.sh: New file.
	* emulparams/elf32tilepro.sh: New file.

Ld testsuite:

2011-06-10  Walter Lee  <walt@tilera.com>

	* ld-elf/eh5.d: Don't run on tile*.
	* ld-srec/srec.exp: xfail on tile*.
	* ld-tilegx/external.s: New file.
	* ld-tilegx/reloc.d: New file.
	* ld-tilegx/reloc.s: New file.
	* ld-tilegx/tilegx.exp: New file.
	* ld-tilepro/external.s: New file.
	* ld-tilepro/reloc.d: New file.
	* ld-tilepro/reloc.s: New file.
	* ld-tilepro/tilepro.exp: New file.

[-- Attachment #2: ld.diff.bz2 --]
[-- Type: application/octet-stream, Size: 1845 bytes --]

[-- Attachment #3: ld_testsuite.diff.bz2 --]
[-- Type: application/octet-stream, Size: 3412 bytes --]

      reply	other threads:[~2011-06-10  6:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-03 21:42 Walter Lee
2011-06-06 20:13 ` Joseph S. Myers
2011-06-10  6:37   ` Walter Lee [this message]

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=4DF1BB8B.2040402@tilera.com \
    --to=walt@tilera.com \
    --cc=binutils@sourceware.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).