From: Ian Lance Taylor <iant@google.com>
To: gcc-patches@gcc.gnu.org, gofrontend-dev@googlegroups.com
Subject: Go testsuite patch committed: Recognize MIPS ABIs
Date: Fri, 01 Apr 2011 00:28:00 -0000 [thread overview]
Message-ID: <mcrk4feolw7.fsf@google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 254 bytes --]
This patch to the Go testsuite driver recognizes the MIPS ABIs. Ran Go
testsuite on x86_64-unknown-linux-gnu. Committed to mainline.
Ian
2011-03-31 Ian Lance Taylor <iant@google.com>
* go.test/go-test.exp (go-set-goarch): Recognize MIPS ABIs.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: patch --]
[-- Type: text/x-diff, Size: 1032 bytes --]
Index: go.test/go-test.exp
===================================================================
--- go.test/go-test.exp (revision 171813)
+++ go.test/go-test.exp (working copy)
@@ -137,6 +137,36 @@ proc go-set-goarch { } {
set goarch "amd64"
}
}
+ "mips-*-*" {
+ if [check_no_compiler_messages mipso32 assembly {
+ #if _MIPS_SIM != _ABIO32
+ #error FOO
+ #endif
+ }] {
+ set goarch "mipso32"
+ } elseif [check_no_compiler_messages mipsn32 assembly {
+ #if _MIPS_SIM != _ABIN32
+ #error FOO
+ #endif
+ }] {
+ set goarch "mipsn32"
+ } elseif [check_no_compiler_messages mipsn64 assembly {
+ #if _MIPS_SIM != _ABI64
+ #error FOO
+ #endif
+ }] {
+ set goarch "mipsn64"
+ } elseif [check_no_compiler_messages mipso64 assembly {
+ #if _MIPS_SIM != _ABIO64
+ #error FOO
+ #endif
+ }] {
+ set goarch "mipso64"
+ } else {
+ perror "$target_triplet: unrecognized MIPS ABI"
+ return ""
+ }
+ }
"sparc*-*-*" {
if [check_effective_target_ilp32] {
set goarch "sparc"
reply other threads:[~2011-04-01 0:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=mcrk4feolw7.fsf@google.com \
--to=iant@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gofrontend-dev@googlegroups.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).