From: Ian Lance Taylor <iant@golang.org>
To: Andrew Chambers <andrewchamberss@gmail.com>
Cc: "gofrontend-dev@googlegroups.com"
<gofrontend-dev@googlegroups.com>,
Lynn Boger <laboger@linux.vnet.ibm.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [gofrontend-dev] Re: GO tools for gccgo cross
Date: Fri, 22 May 2015 23:24:00 -0000 [thread overview]
Message-ID: <CAOyqgcXPMH-YA8yemM4cT0P-PCsJLDFdRVqwPw-GVD44Qpu_LQ@mail.gmail.com> (raw)
In-Reply-To: <9c1f4c29-76b4-4271-9edd-842706e84ef7@googlegroups.com>
On Fri, May 22, 2015 at 3:11 PM, Andrew Chambers
<andrewchamberss@gmail.com> wrote:
>
> I'm not suggesting breaking go conventions, I just think the default if no
> GOARCH is specified then it should match --target.
Sounds good to me.
> Perhaps we could check the symlink name for the target triple if no GOARCH
> is set.
We should probably build it into the tool, perhaps in zdefaultcc.go
created in gotools/Makefile.am.
Ian
next prev parent reply other threads:[~2015-05-22 22:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-03 19:53 Lynn A. Boger
2015-02-03 20:18 ` [gofrontend-dev] " Ian Lance Taylor
[not found] ` <ec194a29-a888-44df-b466-46c7ea06c7f2@googlegroups.com>
2015-03-17 18:27 ` Ian Lance Taylor
2015-04-14 13:14 ` Lynn A. Boger
2015-04-14 14:04 ` Ian Lance Taylor
[not found] ` <21b22da3-4871-4469-83ce-3a2590a3d00a@googlegroups.com>
[not found] ` <555F358B.2060009@linux.vnet.ibm.com>
[not found] ` <CACDP-teX9pCB2zxBp_1f+UQCtyDTVJDAsZacRg50AFd7s0zqWA@mail.gmail.com>
2015-05-22 21:39 ` [gofrontend-dev] " Ian Lance Taylor
[not found] ` <9c1f4c29-76b4-4271-9edd-842706e84ef7@googlegroups.com>
2015-05-22 23:24 ` Ian Lance Taylor [this message]
2015-05-26 16:48 ` Lynn A. Boger
2015-05-26 17:30 ` Ian Lance Taylor
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=CAOyqgcXPMH-YA8yemM4cT0P-PCsJLDFdRVqwPw-GVD44Qpu_LQ@mail.gmail.com \
--to=iant@golang.org \
--cc=andrewchamberss@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gofrontend-dev@googlegroups.com \
--cc=laboger@linux.vnet.ibm.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).