It requires adding -buildmode=c-shared support to cmd/go, cmd/compile, and cmd/link for GOOS=mips and GOOS=mips64. In particular the compiler has to generate position-independent code with the -shared flag. I don't know how much work is involved.

/cc @cherrymui @vstefanovic

For position-independent code, I don't think it's very hard, but do need some work for accessing globals. There is no native PC-relative addressing on MIPS, so we may need to do something like PPC64.
For the linker, does external linking suffice? Or we need to add internal linking?
Add @minux.

@tigranbs do you have an actual Android MIPS device that you are interested in? From what I have been told, there are virtually no MIPS Android devices out in the wild right now.

I have a MIPS Android tablet. They definitely exist. I don't know how
prevalent they are. (It's really terrible and I don't actually use it.)

On Nov 21, 2016 10:58 AM, "Than McIntosh" notifications@github.com wrote:

@tigranbs https://github.com/tigranbs do you have an actual Android
MIPS device that you are interested in? From what I have been told, there
are virtually no MIPS Android devices out in the wild right now.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#17998 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAHEMTy8im-tQkTzBFYNHy0OUtwy8ZCNks5rAb-zgaJpZM4K4O3U
.

There are MIPS-Android devices (tablets, settop boxes, wearables).

Well actually support for Mips kind of devices is just for convince management that Golang is useful for cross platform mobile libraries.

And in fact I think it's not hard to implement ... I'm thinking of trying to compile simple project with plain Go compiler and Android CXX Mips compiler, then based on results I'll try to integrate it with existing Gomobile functionality.

I saw that in code there is fixed values for architectures, just curios, why not to get architectures from Android NDK dynamically and just build project based on flags and NDK compilers for that architecture ? I'll definitely will try to do this !!
I've done that kind of thing for my companies C++ projects, there is no fixed architectures, all depends on Android NDK support, it's easier to upgrade and manage dependencies.

OK, I stand corrected... I'll have to be a bit more careful about what I read on reddit.

Historically the NDK supported 32-bit and 64-bit MIPS, but support for these ABIs was removed in NDK r17. It is a bit sad but I think we could not do anything here. Close.