From: Richard Sandiford <rdsandiford@googlemail.com>
To: "Maciej W. Rozycki" <macro@codesourcery.com>
Cc: <binutils@sourceware.org>
Subject: Re: [PATCH 3/3] MIPS/LD/test: Protected symbol relocation processing
Date: Sun, 12 Aug 2012 18:51:00 -0000 [thread overview]
Message-ID: <87ipcot06c.fsf@talisman.home> (raw)
In-Reply-To: <alpine.DEB.1.10.1208082337460.20608@tp.orcam.me.uk> (Maciej W. Rozycki's message of "Wed, 8 Aug 2012 23:50:07 +0100")
"Maciej W. Rozycki" <macro@codesourcery.com> writes:
> 2012-08-08 Maciej W. Rozycki <macro@codesourcery.com>
>
> ld/testsuite/
> * ld-mips-elf/export-class-call16-o32.dd: New test.
> * ld-mips-elf/export-class-call16-o32-irix.dd: New test.
> * ld-mips-elf/export-class-call16-o32.gd: New test.
> * ld-mips-elf/export-class-call16-n32.dd: New test.
> * ld-mips-elf/export-class-call16-n32.gd: New test.
> * ld-mips-elf/export-class-call16-n64.dd: New test.
> * ld-mips-elf/export-class-call16-n64.gd: New test.
> * ld-mips-elf/export-class-call16-def.s: New test source.
> * ld-mips-elf/export-class-call16-o32.s: New test source.
> * ld-mips-elf/export-class-call16-n32.s: New test source.
> * ld-mips-elf/export-class-call16-n64.s: New test source.
> * ld-mips-elf/export-class-call16.ld: New test linker script.
> * ld-mips-elf/mips-elf.exp: Run the new tests.
OK.
next prev parent reply other threads:[~2012-08-12 18:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 22:49 [PATCH 1/3] MIPS/BFD: Correct protected " Maciej W. Rozycki
2012-08-08 22:50 ` [PATCH 2/3] MIPS/BFD: Correct IRIX 6 DT_MIPS_OPTIONS processing Maciej W. Rozycki
2012-08-12 18:50 ` Richard Sandiford
2012-08-13 14:10 ` Maciej W. Rozycki
2012-08-13 19:44 ` Richard Sandiford
2012-08-13 19:53 ` Maciej W. Rozycki
2012-08-09 1:28 ` [PATCH 3/3] MIPS/LD/test: Protected symbol relocation processing Maciej W. Rozycki
2012-08-12 18:51 ` Richard Sandiford [this message]
2012-08-13 21:41 ` Maciej W. Rozycki
2012-08-12 18:43 ` [PATCH 1/3] MIPS/BFD: Correct protected " Richard Sandiford
2012-08-13 13:24 ` Maciej W. Rozycki
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=87ipcot06c.fsf@talisman.home \
--to=rdsandiford@googlemail.com \
--cc=binutils@sourceware.org \
--cc=macro@codesourcery.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).