From: "Lynn A. Boger" <laboger@linux.vnet.ibm.com>
To: Ian Lance Taylor <iant@golang.org>,
Andrew Chambers <andrewchamberss@gmail.com>
Cc: "gofrontend-dev@googlegroups.com"
<gofrontend-dev@googlegroups.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [gofrontend-dev] Re: GO tools for gccgo cross
Date: Tue, 26 May 2015 16:48:00 -0000 [thread overview]
Message-ID: <55649C9A.3050604@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAOyqgcXPMH-YA8yemM4cT0P-PCsJLDFdRVqwPw-GVD44Qpu_LQ@mail.gmail.com>
On 05/22/2015 05:50 PM, Ian Lance Taylor wrote:
> 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.
I'm not sure exactly what is meant here.
If you build a native gccgo and its corresponding native go tool, I
think it should have the plain name 'go' and accept any GOARCH and GOOS
values to indicate the cross compile target, and use the correct cross
gccgo (via target triple name) based on that. golang determines the
cross compiler based on the GOOS and GOARCH settings and I think it
should work the same way when using gccgo if possible.
If you build a cross gccgo and want to have a cross go tool dedicated to
that cross gccgo then the cross go tool it makes sense to have the
target triple name so it is clear it is not the native go tool.
(Realize in this case the native gccgo will have to have been built
since any go tool, cross or not, has to run natively and have been built
using the native gccgo.)
What symlink do you mean? On one system (like a build machine) there
could be multiple cross gccgo compilers and therefore multiple cross go
tools for those compilers, so then what is the symlink and what would it
be set to?
> Ian
>
>
next prev parent reply other threads:[~2015-05-26 16:17 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
2015-05-26 16:48 ` Lynn A. Boger [this message]
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=55649C9A.3050604@linux.vnet.ibm.com \
--to=laboger@linux.vnet.ibm.com \
--cc=andrewchamberss@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gofrontend-dev@googlegroups.com \
--cc=iant@golang.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).