From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] Go: CGO and Plan 9
Date: Sat, 2 Feb 2013 17:52:39 +0200 [thread overview]
Message-ID: <6687527721a908cf83dbb33b10206092@proxima.alt.za> (raw)
In-Reply-To: <20130202152419.GA30387@dinah>
> The C compilers in the Go toolchain pass everything on the
> stack and return the result in a register.
>
> The Go compilers pass everything on the stack including the
> output parameters. No registers are involved in the calling
> convention.
That isn't a big deal, in my case, because the language handled by the
C compilers in the Go toolchain is the same as Plan 9 native C, so,
within reason, I would expect the Go toolchain to compile the OpenLDAP
programs successfully, it doesn't matter if they are not consistent
with the Plan 9 native toolchain.
I suppose this raises the first concrete question: how do I get the
"go" tool to compile the OpenLDAP libraries (and possibly programs) in
some sensible fashion? It would be distressing to have to increase
the autoconf hell at this point. A partial answer to this would be
preferable to a blunt "You should not be wanting to do this".
Again, thanks for the contributions, the fog isn't visibly lifting
yet, but the feeling's there :-)
++L
PS: Note that even corrections of crossed wires have been extremely
helpful.
PPS: Eventually, there needs to be ONE Go + C + ASM toolchain. It may
take years and a lot of TLC to produce, but any other outcome, with
the possible exception that something will obsolete each of the above
languages, is a frightening prospect in the long term. Let's keep
that in mind and not contribute intentionally and unnecessarily to the
divergence.
next prev parent reply other threads:[~2013-02-02 15:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-30 4:41 lucio
2013-02-01 17:52 ` Pavel Zholkover
2013-02-02 14:28 ` Aram Hăvărneanu
2013-02-02 15:24 ` Anthony Martin
2013-02-02 15:52 ` lucio [this message]
2013-02-02 15:41 ` lucio
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=6687527721a908cf83dbb33b10206092@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).