www.digitalmars.com         C & C++   DMDScript  

digitalmars.D.announce - [Tutorial][Binaries] gdc for android

reply Johannes Pfau <nospam example.com> writes:
Hi,
I tried to rebuild the android ndk with gdc and documented the build
process at https://bitbucket.org/goshawk/gdc/wiki/GDC%20on%20Android

The tutorial explains how to build a gdc cross compiler for android. It
uses GCC 4.6.2, a recent binutils snapshot and additionally provides a
recent gdb 7.4.

32bit linux binaries are also available here:
http://www.mediafire.com/?2cex2faqx327l
Download the android ndk r7 and extract the gdc 7z file in
android-ndk-r7/toolchains/

What's working:
I couldn't test the compiler yet and I hope someone else will provide
feedback, but the basic gdc compiler should work. druntime may or may
not work, but it's distributed so that can be tested.
Phobos is not being built yet.

Known bugs/TODO:

You need to build all D code with -fno-section-anchors, see
https://bitbucket.org/goshawk/gdc/issue/120/fsection-anchors-broken-on-arm

build-druntime.patch needs to be integrated with gdc. See
https://gist.github.com/1739039
There are basically 3 things this patch does:
* Currently gdc checks for __libc_stack_end as that's used by
  druntime. This function is only available in glibc, but bionic
  provides a similar function: __get_stack_base. The patch currently
  simply replaces __libc_stack_end. We need some way to detect if we
  build for bionic, so we can properly version this code. It should
  also be tested to verify it is working correctly
* Building gcc/config/unix.d fails, so the patch simply skips that
  file. This should be investigated further and fixed correctly.
* Disables phobos for now, although I think I just disabled building the
  final library and the object files are still being built.

gdbserver is not being built for some reason. Had no time to
investigate that yet.
Feb 04 2012
next sibling parent "Nick Sabalausky" <a a.a> writes:
"Johannes Pfau" <nospam example.com> wrote in message 
news:20120204203109.26c9a80b jpf-laptop...

 Hi,
 I tried to rebuild the android ndk with gdc and documented the build
 process at https://bitbucket.org/goshawk/gdc/wiki/GDC%20on%20Android

 The tutorial explains how to build a gdc cross compiler for android. It
 uses GCC 4.6.2, a recent binutils snapshot and additionally provides a
 recent gdb 7.4.

 32bit linux binaries are also available here:
 http://www.mediafire.com/?2cex2faqx327l
 Download the android ndk r7 and extract the gdc 7z file in
 android-ndk-r7/toolchains/

 What's working:
 I couldn't test the compiler yet and I hope someone else will provide
 feedback, but the basic gdc compiler should work. druntime may or may
 not work, but it's distributed so that can be tested.
 Phobos is not being built yet.

 Known bugs/TODO:

 You need to build all D code with -fno-section-anchors, see
 https://bitbucket.org/goshawk/gdc/issue/120/fsection-anchors-broken-on-arm

 build-druntime.patch needs to be integrated with gdc. See
 https://gist.github.com/1739039
 There are basically 3 things this patch does:
 * Currently gdc checks for __libc_stack_end as that's used by
  druntime. This function is only available in glibc, but bionic
  provides a similar function: __get_stack_base. The patch currently
  simply replaces __libc_stack_end. We need some way to detect if we
  build for bionic, so we can properly version this code. It should
  also be tested to verify it is working correctly
 * Building gcc/config/unix.d fails, so the patch simply skips that
  file. This should be investigated further and fixed correctly.
 * Disables phobos for now, although I think I just disabled building the
  final library and the object files are still being built.

 gdbserver is not being built for some reason. Had no time to
 investigate that yet.


Awesome! I look forward to giving it a try.
Feb 04 2012
prev sibling next sibling parent reply Iain Buclaw <ibuclaw ubuntu.com> writes:
On 4 February 2012 21:59, Manu <turkeyman gmail.com> wrote:

 On 4 February 2012 21:31, Johannes Pfau <nospam example.com> wrote:

 Hi,
 I tried to rebuild the android ndk with gdc and documented the build
 process at https://bitbucket.org/goshawk/gdc/wiki/GDC%20on%20Android

 The tutorial explains how to build a gdc cross compiler for android. It
 uses GCC 4.6.2, a recent binutils snapshot and additionally provides a
 recent gdb 7.4.

 32bit linux binaries are also available here:
 http://www.mediafire.com/?2cex2faqx327l
 Download the android ndk r7 and extract the gdc 7z file in
 android-ndk-r7/toolchains/

 What's working:
 I couldn't test the compiler yet and I hope someone else will provide
 feedback, but the basic gdc compiler should work. druntime may or may
 not work, but it's distributed so that can be tested.
 Phobos is not being built yet.

 Known bugs/TODO:

 You need to build all D code with -fno-section-anchors, see
 https://bitbucket.org/goshawk/gdc/issue/120/fsection-anchors-broken-on-a=




rm

 build-druntime.patch needs to be integrated with gdc. See
 https://gist.github.com/1739039
 There are basically 3 things this patch does:
 * Currently gdc checks for __libc_stack_end as that's used by
 =A0druntime. This function is only available in glibc, but bionic
 =A0provides a similar function: __get_stack_base. The patch currently
 =A0simply replaces __libc_stack_end. We need some way to detect if we
 =A0build for bionic, so we can properly version this code. It should
 =A0also be tested to verify it is working correctly
 * Building gcc/config/unix.d fails, so the patch simply skips that
 =A0file. This should be investigated further and fixed correctly.
 * Disables phobos for now, although I think I just disabled building the
 =A0final library and the object files are still being built.

 gdbserver is not being built for some reason. Had no time to
 investigate that yet.



 Amazing!
 Do you know how/could you produce binaries for the mingw host? The androi=


d

 toolchain for windows can only be built from linux according to the
 toolchain docs last time I tried to build it.


Virtualbox. :=FE

--=20
Iain Buclaw

*(p < e ? p++ : p) =3D (c & 0x0f) + '0';
Feb 04 2012
parent reply Johannes Pfau <nospam example.com> writes:
Am Sat, 4 Feb 2012 22:17:54 +0000
schrieb Iain Buclaw <ibuclaw ubuntu.com>:


 On 4 February 2012 21:59, Manu <turkeyman gmail.com> wrote:

 On 4 February 2012 21:31, Johannes Pfau <nospam example.com> wrote:

 Hi,
 I tried to rebuild the android ndk with gdc and documented the
 build process at
 https://bitbucket.org/goshawk/gdc/wiki/GDC%20on%20Android

 The tutorial explains how to build a gdc cross compiler for
 android. It uses GCC 4.6.2, a recent binutils snapshot and
 additionally provides a recent gdb 7.4.

 32bit linux binaries are also available here:
 http://www.mediafire.com/?2cex2faqx327l
 Download the android ndk r7 and extract the gdc 7z file in
 android-ndk-r7/toolchains/

 What's working:
 I couldn't test the compiler yet and I hope someone else will
 provide feedback, but the basic gdc compiler should work. druntime
 may or may not work, but it's distributed so that can be tested.
 Phobos is not being built yet.

 Known bugs/TODO:

 You need to build all D code with -fno-section-anchors, see
 https://bitbucket.org/goshawk/gdc/issue/120/fsection-anchors-broken-on=






-arm

 build-druntime.patch needs to be integrated with gdc. See
 https://gist.github.com/1739039
 There are basically 3 things this patch does:
 * Currently gdc checks for __libc_stack_end as that's used by
 =C2=A0druntime. This function is only available in glibc, but bionic
 =C2=A0provides a similar function: __get_stack_base. The patch current=






ly

 =C2=A0simply replaces __libc_stack_end. We need some way to detect if =






we

 =C2=A0build for bionic, so we can properly version this code. It should
 =C2=A0also be tested to verify it is working correctly
 * Building gcc/config/unix.d fails, so the patch simply skips that
 =C2=A0file. This should be investigated further and fixed correctly.
 * Disables phobos for now, although I think I just disabled
 building the final library and the object files are still being
 built.

 gdbserver is not being built for some reason. Had no time to
 investigate that yet.



 Amazing!
 Do you know how/could you produce binaries for the mingw host? The
 android toolchain for windows can only be built from linux
 according to the toolchain docs last time I tried to build it.


=20
 Virtualbox. :=C3=BE
=20


According to the docs I just have to pass --mingw to the build script
and use the windows ndk as a base. I'll try this tomorrow, but I'd be
surprised if it really was that easy ;-)
Feb 04 2012
parent reply Manu <turkeyman gmail.com> writes:
On 5 February 2012 01:17, Johannes Pfau <nospam example.com> wrote:


 Am Sat, 4 Feb 2012 22:17:54 +0000
 schrieb Iain Buclaw <ibuclaw ubuntu.com>:


 On 4 February 2012 21:59, Manu <turkeyman gmail.com> wrote:

 On 4 February 2012 21:31, Johannes Pfau <nospam example.com> wrote:

 Hi,
 I tried to rebuild the android ndk with gdc and documented the
 build process at
 https://bitbucket.org/goshawk/gdc/wiki/GDC%20on%20Android

 The tutorial explains how to build a gdc cross compiler for
 android. It uses GCC 4.6.2, a recent binutils snapshot and
 additionally provides a recent gdb 7.4.

 32bit linux binaries are also available here:
 http://www.mediafire.com/?2cex2faqx327l
 Download the android ndk r7 and extract the gdc 7z file in
 android-ndk-r7/toolchains/

 What's working:
 I couldn't test the compiler yet and I hope someone else will
 provide feedback, but the basic gdc compiler should work. druntime
 may or may not work, but it's distributed so that can be tested.
 Phobos is not being built yet.

 Known bugs/TODO:

 You need to build all D code with -fno-section-anchors, see






 https://bitbucket.org/goshawk/gdc/issue/120/fsection-anchors-broken-on-ar=


m

 build-druntime.patch needs to be integrated with gdc. See
 https://gist.github.com/1739039
 There are basically 3 things this patch does:
 * Currently gdc checks for __libc_stack_end as that's used by
  druntime. This function is only available in glibc, but bionic
  provides a similar function: __get_stack_base. The patch currently
  simply replaces __libc_stack_end. We need some way to detect if we
  build for bionic, so we can properly version this code. It should
  also be tested to verify it is working correctly
 * Building gcc/config/unix.d fails, so the patch simply skips that
  file. This should be investigated further and fixed correctly.
 * Disables phobos for now, although I think I just disabled
 building the final library and the object files are still being
 built.

 gdbserver is not being built for some reason. Had no time to
 investigate that yet.



 Amazing!
 Do you know how/could you produce binaries for the mingw host? The
 android toolchain for windows can only be built from linux
 according to the toolchain docs last time I tried to build it.


 Virtualbox. :=C3=BE


 According to the docs I just have to pass --mingw to the build script
 and use the windows ndk as a base. I'll try this tomorrow, but I'd be
 surprised if it really was that easy ;-)


Me too, but good luck!
Here's hoping... :P
Feb 04 2012
parent reply Johannes Pfau <nospam example.com> writes:
Am Sun, 5 Feb 2012 02:31:01 +0200
schrieb Manu <turkeyman gmail.com>:


 On 5 February 2012 01:17, Johannes Pfau <nospam example.com> wrote:
=20

 Am Sat, 4 Feb 2012 22:17:54 +0000
 schrieb Iain Buclaw <ibuclaw ubuntu.com>:


 On 4 February 2012 21:59, Manu <turkeyman gmail.com> wrote:

 On 4 February 2012 21:31, Johannes Pfau <nospam example.com>
 wrote:

 Hi,
 I tried to rebuild the android ndk with gdc and documented the
 build process at
 https://bitbucket.org/goshawk/gdc/wiki/GDC%20on%20Android

 The tutorial explains how to build a gdc cross compiler for
 android. It uses GCC 4.6.2, a recent binutils snapshot and
 additionally provides a recent gdb 7.4.

 32bit linux binaries are also available here:
 http://www.mediafire.com/?2cex2faqx327l
 Download the android ndk r7 and extract the gdc 7z file in
 android-ndk-r7/toolchains/

 What's working:
 I couldn't test the compiler yet and I hope someone else will
 provide feedback, but the basic gdc compiler should work.
 druntime may or may not work, but it's distributed so that can
 be tested. Phobos is not being built yet.

 Known bugs/TODO:

 You need to build all D code with -fno-section-anchors, see






 https://bitbucket.org/goshawk/gdc/issue/120/fsection-anchors-broken-on-=




arm

 build-druntime.patch needs to be integrated with gdc. See
 https://gist.github.com/1739039
 There are basically 3 things this patch does:
 * Currently gdc checks for __libc_stack_end as that's used by
  druntime. This function is only available in glibc, but bionic
  provides a similar function: __get_stack_base. The patch
 currently simply replaces __libc_stack_end. We need some way
 to detect if we build for bionic, so we can properly version
 this code. It should also be tested to verify it is working
 correctly
 * Building gcc/config/unix.d fails, so the patch simply skips
 that file. This should be investigated further and fixed
 correctly.
 * Disables phobos for now, although I think I just disabled
 building the final library and the object files are still being
 built.

 gdbserver is not being built for some reason. Had no time to
 investigate that yet.



 Amazing!
 Do you know how/could you produce binaries for the mingw host?
 The android toolchain for windows can only be built from linux
 according to the toolchain docs last time I tried to build it.


 Virtualbox. :=C3=BE


 According to the docs I just have to pass --mingw to the build
 script and use the windows ndk as a base. I'll try this tomorrow,
 but I'd be surprised if it really was that easy ;-)


=20
 Me too, but good luck!
 Here's hoping... :P
=20


somehow the build scripts pick up the wrong compiler and I have no clue
why.

-------------------
configure:2642: checking for i586-mingw32msvc-gcc
configure:2669: result: gcc
configure:2938: checking for C compiler version
configure:2947: gcc --version >&5
gcc (Debian 4.6.1-4) 4.6.1
-------------------

I will probably need some more time to get this working...
Feb 05 2012
parent reply Johannes Pfau <nospam example.com> writes:
Am Sun, 5 Feb 2012 18:04:12 +0100
schrieb Johannes Pfau <nospam example.com>:


 I will probably need some more time to get this working...
 


I have some good news:
http://www.mediafire.com/?107we120sh3xx

I fixed that problem and then the whole build worked fine. I'll post
build instructions soon, but the binaries are ready. I only did a
simple gdc -c test.d to check the compiler, but it seems to work.

Linking against druntime fails, as it uses functions which are not
available on Android (backtrace, signal stuff).

I also built a simple hello world on linux (printf, no runtime) and ran
it on my android phone, and it worked!

In case you haven't used GDC without runtime before, a short
introduction:

* use gdc -nophoboslib to make gdc not link against phobos (and afaik,
  druntime)
* theres also -nostdlib in case you need it

* You'll get an error about a missing _Dmodule_ref symbol. That symbol
  is used by module constructors and not generated by gdc if
  -nophoboslib was passed. As long as you don't run the module
  constructors, you can add a fake _Dmodule_ref in a .c file:

------------
void* _Dmodule_ref;
------------

* The compiler defines version(Android)

Here's my hello world:
------------
version(Android)
{
    pragma(msg, "Hello Android!");
}

extern(C)
{
    int printf(in char* format, ...);
}

extern(C) void main()
{
    printf("Hello, %s!\n".ptr, "Android".ptr);
}
------------

compile the _Dmodule_ref into hack.o, then use
gdc -nophoboslib hello.d hack.o
Feb 05 2012
next sibling parent reply =?ISO-8859-1?Q?Alex_R=F8nne_Petersen?= <xtzgzorex gmail.com> writes:
On 02/05/2012 11:04 PM, Johannes Pfau wrote:

 Am Sun, 5 Feb 2012 18:04:12 +0100
 schrieb Johannes Pfau<nospam example.com>:


 I will probably need some more time to get this working...


 I have some good news:
 http://www.mediafire.com/?107we120sh3xx

 I fixed that problem and then the whole build worked fine. I'll post
 build instructions soon, but the binaries are ready. I only did a
 simple gdc -c test.d to check the compiler, but it seems to work.

 Linking against druntime fails, as it uses functions which are not
 available on Android (backtrace, signal stuff).

 I also built a simple hello world on linux (printf, no runtime) and ran
 it on my android phone, and it worked!

 In case you haven't used GDC without runtime before, a short
 introduction:

 * use gdc -nophoboslib to make gdc not link against phobos (and afaik,
    druntime)
 * theres also -nostdlib in case you need it

 * You'll get an error about a missing _Dmodule_ref symbol. That symbol
    is used by module constructors and not generated by gdc if
    -nophoboslib was passed. As long as you don't run the module
    constructors, you can add a fake _Dmodule_ref in a .c file:

 ------------
 void* _Dmodule_ref;
 ------------

 * The compiler defines version(Android)

 Here's my hello world:
 ------------
 version(Android)
 {
      pragma(msg, "Hello Android!");
 }

 extern(C)
 {
      int printf(in char* format, ...);
 }

 extern(C) void main()
 {
      printf("Hello, %s!\n".ptr, "Android".ptr);
 }
 ------------

 compile the _Dmodule_ref into hack.o, then use
 gdc -nophoboslib hello.d hack.o


Can we standardize that Android version identifier? Would be good to 
have it on dlang.org/version.html.

-- 
- Alex
Feb 05 2012
parent maarten van damme <maartenvd1994 gmail.com> writes:
wow, great news for my phone :)
I've read another blogpost about someone trying to achieve the same, had
something to do with "between ideals", I'll google it up if you need it.
he had a github repo with some "ugly hacks" to make druntime work for
android, maybe this can be looked into?

2012/2/5 Alex R=F8nne Petersen <xtzgzorex gmail.com>


 On 02/05/2012 11:04 PM, Johannes Pfau wrote:


 Am Sun, 5 Feb 2012 18:04:12 +0100
 schrieb Johannes Pfau<nospam example.com>:

  I will probably need some more time to get this working...


 I have some good news:
 http://www.mediafire.com/?**107we120sh3xx<http://www.mediafire.com/?107w=




e120sh3xx>

 I fixed that problem and then the whole build worked fine. I'll post
 build instructions soon, but the binaries are ready. I only did a
 simple gdc -c test.d to check the compiler, but it seems to work.

 Linking against druntime fails, as it uses functions which are not
 available on Android (backtrace, signal stuff).

 I also built a simple hello world on linux (printf, no runtime) and ran
 it on my android phone, and it worked!

 In case you haven't used GDC without runtime before, a short
 introduction:

 * use gdc -nophoboslib to make gdc not link against phobos (and afaik,
   druntime)
 * theres also -nostdlib in case you need it

 * You'll get an error about a missing _Dmodule_ref symbol. That symbol
   is used by module constructors and not generated by gdc if
   -nophoboslib was passed. As long as you don't run the module
   constructors, you can add a fake _Dmodule_ref in a .c file:

 ------------
 void* _Dmodule_ref;
 ------------

 * The compiler defines version(Android)

 Here's my hello world:
 ------------
 version(Android)
 {
     pragma(msg, "Hello Android!");
 }

 extern(C)
 {
     int printf(in char* format, ...);
 }

 extern(C) void main()
 {
     printf("Hello, %s!\n".ptr, "Android".ptr);
 }
 ------------

 compile the _Dmodule_ref into hack.o, then use
 gdc -nophoboslib hello.d hack.o


 Can we standardize that Android version identifier? Would be good to have
 it on dlang.org/version.html.

 --
 - Alex





 Feb 05 2012



prev sibling next sibling parent  Manu <turkeyman gmail.com>  writes:


On 6 February 2012 00:04, Johannes Pfau <nospam example.com> wrote:


 Am Sun, 5 Feb 2012 18:04:12 +0100
 schrieb Johannes Pfau <nospam example.com>:


 I will probably need some more time to get this working...


 I have some good news:
 http://www.mediafire.com/?107we120sh3xx

 I fixed that problem and then the whole build worked fine. I'll post
 build instructions soon, but the binaries are ready. I only did a
 simple gdc -c test.d to check the compiler, but it seems to work.

 Linking against druntime fails, as it uses functions which are not
 available on Android (backtrace, signal stuff).

 I also built a simple hello world on linux (printf, no runtime) and ran
 it on my android phone, and it worked!

 In case you haven't used GDC without runtime before, a short
 introduction:

 * use gdc -nophoboslib to make gdc not link against phobos (and afaik,
  druntime)
 * theres also -nostdlib in case you need it

 * You'll get an error about a missing _Dmodule_ref symbol. That symbol
  is used by module constructors and not generated by gdc if
  -nophoboslib was passed. As long as you don't run the module
  constructors, you can add a fake _Dmodule_ref in a .c file:

 ------------
 void* _Dmodule_ref;
 ------------

 * The compiler defines version(Android)

 Here's my hello world:
 ------------
 version(Android)
 {
    pragma(msg, "Hello Android!");
 }

 extern(C)
 {
    int printf(in char* format, ...);
 }

 extern(C) void main()
 {
    printf("Hello, %s!\n".ptr, "Android".ptr);
 }
 ------------

 compile the _Dmodule_ref into hack.o, then use
 gdc -nophoboslib hello.d hack.o


Amazing! You sir, are a genius!
I'm gonna have to have some fun with that after work tomorrow :)

I reckon this binary distro should be put on d-p-l somewhere obvious.



 Feb 05 2012



prev sibling next sibling parent reply Manu <turkeyman gmail.com>  writes:


On 6 February 2012 02:25, Manu <turkeyman gmail.com> wrote:


 On 6 February 2012 00:04, Johannes Pfau <nospam example.com> wrote:


 Am Sun, 5 Feb 2012 18:04:12 +0100
 schrieb Johannes Pfau <nospam example.com>:


 I will probably need some more time to get this working...


 I have some good news:
 http://www.mediafire.com/?107we120sh3xx

 I fixed that problem and then the whole build worked fine. I'll post
 build instructions soon, but the binaries are ready. I only did a
 simple gdc -c test.d to check the compiler, but it seems to work.

 Linking against druntime fails, as it uses functions which are not
 available on Android (backtrace, signal stuff).

 I also built a simple hello world on linux (printf, no runtime) and ran
 it on my android phone, and it worked!

 In case you haven't used GDC without runtime before, a short
 introduction:

 * use gdc -nophoboslib to make gdc not link against phobos (and afaik,
  druntime)
 * theres also -nostdlib in case you need it

 * You'll get an error about a missing _Dmodule_ref symbol. That symbol
  is used by module constructors and not generated by gdc if
  -nophoboslib was passed. As long as you don't run the module
  constructors, you can add a fake _Dmodule_ref in a .c file:

 ------------
 void* _Dmodule_ref;
 ------------

 * The compiler defines version(Android)

 Here's my hello world:
 ------------
 version(Android)
 {
    pragma(msg, "Hello Android!");
 }

 extern(C)
 {
    int printf(in char* format, ...);
 }

 extern(C) void main()
 {
    printf("Hello, %s!\n".ptr, "Android".ptr);
 }
 ------------

 compile the _Dmodule_ref into hack.o, then use
 gdc -nophoboslib hello.d hack.o


 Amazing! You sir, are a genius!
 I'm gonna have to have some fun with that after work tomorrow :)

 I reckon this binary distro should be put on d-p-l somewhere obvious.


I just tried with -mfpu=neon, which should allow GCC to generate neon
opcodes for the simd stuff, but it didn't seem to want to do that. In fact
it generates really horrible code where it CALLS an intrinsic for each
float in the vector...
Any idea why this wouldn't work out of the box?

I wanted to add ARM support to my std.simd work here as a better proof of
concept.

Iain: was there anything particularly special you needed to do to hook the
x86 SSE stuff to GDC which would need to be duplicated for ARM?
gcc.builtins doesn't seen to have any ARM intrinsics in there either...



 Feb 05 2012



  parent reply Johannes Pfau <nospam example.com>  writes:


Am Mon, 6 Feb 2012 03:07:31 +0200
schrieb Manu <turkeyman gmail.com>:


 On 6 February 2012 02:25, Manu <turkeyman gmail.com> wrote:
 

 On 6 February 2012 00:04, Johannes Pfau <nospam example.com> wrote:


 Am Sun, 5 Feb 2012 18:04:12 +0100
 schrieb Johannes Pfau <nospam example.com>:


 I will probably need some more time to get this working...


 I have some good news:
 http://www.mediafire.com/?107we120sh3xx

 I fixed that problem and then the whole build worked fine. I'll
 post build instructions soon, but the binaries are ready. I only
 did a simple gdc -c test.d to check the compiler, but it seems to
 work.

 Linking against druntime fails, as it uses functions which are not
 available on Android (backtrace, signal stuff).

 I also built a simple hello world on linux (printf, no runtime)
 and ran it on my android phone, and it worked!

 In case you haven't used GDC without runtime before, a short
 introduction:

 * use gdc -nophoboslib to make gdc not link against phobos (and
 afaik, druntime)
 * theres also -nostdlib in case you need it

 * You'll get an error about a missing _Dmodule_ref symbol. That
 symbol is used by module constructors and not generated by gdc if
  -nophoboslib was passed. As long as you don't run the module
  constructors, you can add a fake _Dmodule_ref in a .c file:

 ------------
 void* _Dmodule_ref;
 ------------

 * The compiler defines version(Android)

 Here's my hello world:
 ------------
 version(Android)
 {
    pragma(msg, "Hello Android!");
 }

 extern(C)
 {
    int printf(in char* format, ...);
 }

 extern(C) void main()
 {
    printf("Hello, %s!\n".ptr, "Android".ptr);
 }
 ------------

 compile the _Dmodule_ref into hack.o, then use
 gdc -nophoboslib hello.d hack.o


 Amazing! You sir, are a genius!
 I'm gonna have to have some fun with that after work tomorrow :)

 I reckon this binary distro should be put on d-p-l somewhere
 obvious.


 
 I just tried with -mfpu=neon, which should allow GCC to generate neon
 opcodes for the simd stuff, but it didn't seem to want to do that. In
 fact it generates really horrible code where it CALLS an intrinsic
 for each float in the vector...
 Any idea why this wouldn't work out of the box?


The android toolchain configures gcc with: += --with-float=soft
--with-fpu=vfp --with-arch=armv5te

I could try to build an optimized build, but then you'll have to tell
me what processor you're using. Cortex A8?

I'm not sure if you can override that at runtime. You could probably
try:
-mfloat-abi=hard -mcpu=cortex-a8 -march=armv7-a -mfpu=neon 


 I wanted to add ARM support to my std.simd work here as a better
 proof of concept.
 
 Iain: was there anything particularly special you needed to do to
 hook the x86 SSE stuff to GDC which would need to be duplicated for
 ARM? gcc.builtins doesn't seen to have any ARM intrinsics in there
 either...
 





 Feb 05 2012



 next sibling parent reply Andrew Wiley <wiley.andrew.j gmail.com>  writes:


On Mon, Feb 6, 2012 at 1:40 AM, Johannes Pfau <nospam example.com> wrote:

 Am Mon, 6 Feb 2012 03:07:31 +0200
 schrieb Manu <turkeyman gmail.com>:


 On 6 February 2012 02:25, Manu <turkeyman gmail.com> wrote:


 On 6 February 2012 00:04, Johannes Pfau <nospam example.com> wrote:


 Am Sun, 5 Feb 2012 18:04:12 +0100
 schrieb Johannes Pfau <nospam example.com>:


 I will probably need some more time to get this working...


 I have some good news:
 http://www.mediafire.com/?107we120sh3xx

 I fixed that problem and then the whole build worked fine. I'll
 post build instructions soon, but the binaries are ready. I only
 did a simple gdc -c test.d to check the compiler, but it seems to
 work.

 Linking against druntime fails, as it uses functions which are not
 available on Android (backtrace, signal stuff).

 I also built a simple hello world on linux (printf, no runtime)
 and ran it on my android phone, and it worked!

 In case you haven't used GDC without runtime before, a short
 introduction:

 * use gdc -nophoboslib to make gdc not link against phobos (and
 afaik, druntime)
 * theres also -nostdlib in case you need it

 * You'll get an error about a missing _Dmodule_ref symbol. That
 symbol is used by module constructors and not generated by gdc if
 =A0-nophoboslib was passed. As long as you don't run the module
 =A0constructors, you can add a fake _Dmodule_ref in a .c file:

 ------------
 void* _Dmodule_ref;
 ------------

 * The compiler defines version(Android)

 Here's my hello world:
 ------------
 version(Android)
 {
 =A0 =A0pragma(msg, "Hello Android!");
 }

 extern(C)
 {
 =A0 =A0int printf(in char* format, ...);
 }

 extern(C) void main()
 {
 =A0 =A0printf("Hello, %s!\n".ptr, "Android".ptr);
 }
 ------------

 compile the _Dmodule_ref into hack.o, then use
 gdc -nophoboslib hello.d hack.o


 Amazing! You sir, are a genius!
 I'm gonna have to have some fun with that after work tomorrow :)

 I reckon this binary distro should be put on d-p-l somewhere
 obvious.


 I just tried with -mfpu=3Dneon, which should allow GCC to generate neon
 opcodes for the simd stuff, but it didn't seem to want to do that. In
 fact it generates really horrible code where it CALLS an intrinsic
 for each float in the vector...
 Any idea why this wouldn't work out of the box?


 The android toolchain configures gcc with: +=3D --with-float=3Dsoft
 --with-fpu=3Dvfp --with-arch=3Darmv5te

 I could try to build an optimized build, but then you'll have to tell
 me what processor you're using. Cortex A8?

 I'm not sure if you can override that at runtime. You could probably
 try:
 -mfloat-abi=3Dhard -mcpu=3Dcortex-a8 -march=3Darmv7-a -mfpu=3Dneon


Actually, if the Android default is to build against softfloat ABI,
you may be stuck with it. If Android doesn't require hardfloat to run
and doesn't let developers provide multiple binaries for different
platforms (which it might - I don't know), things get very hard.

Also, with NEON, one of the things you don't really hear until you
start working with these is that NEON isn't actually required in most
if not all of the ARM CPU specs. I've specifically dealt with the
Tegra 2, which is used in a lot of phones and has no NEON support even
though it's ARM Cortex-A9.



 Feb 05 2012



  parent reply Johannes Pfau <nospam example.com>  writes:


Am Mon, 6 Feb 2012 01:48:32 -0600
schrieb Andrew Wiley <wiley.andrew.j gmail.com>:


 
 Actually, if the Android default is to build against softfloat ABI,
 you may be stuck with it. If Android doesn't require hardfloat to run
 and doesn't let developers provide multiple binaries for different
 platforms (which it might - I don't know), things get very hard.
 
 Also, with NEON, one of the things you don't really hear until you
 start working with these is that NEON isn't actually required in most
 if not all of the ARM CPU specs. I've specifically dealt with the
 Tegra 2, which is used in a lot of phones and has no NEON support even
 though it's ARM Cortex-A9.


There's a official armv7-a ABI for android, it doesn't use 'hard', but
at least 'softfp' instead of 'soft'.

Just found the relevant documentation: See
android-ndk-r7/docs/STANDALONE-TOOLCHAIN.html 4/ ABI Compatibility:
------------------------
If you want to target the 'armeabi-v7a' ABI, you will need ensure that
the following two flags are being used:

  CFLAGS='-march=armv7-a -mfloat-abi=softfp'

If you want to use Neon instructions, you will need one more compiler
flag:

  CFLAGS='-march=armv7-a -mfloat-abi=softfp -mfpu=neon'

Also, is is *required* to use the following linker flags that routes
around a CPU bug in some Cortex-A8 implementations:

  LDFLAGS='-Wl,--fix-cortex-a8'
------------------------
so according to those docs, you simply pass those flags to the
compiler, no need to recompile the compiler.



 Feb 06 2012



 next sibling parent  Iain Buclaw <ibuclaw ubuntu.com>  writes:


On 6 February 2012 08:11, Johannes Pfau <nospam example.com> wrote:

 Am Mon, 6 Feb 2012 01:48:32 -0600
 schrieb Andrew Wiley <wiley.andrew.j gmail.com>:


 Actually, if the Android default is to build against softfloat ABI,
 you may be stuck with it. If Android doesn't require hardfloat to run
 and doesn't let developers provide multiple binaries for different
 platforms (which it might - I don't know), things get very hard.

 Also, with NEON, one of the things you don't really hear until you
 start working with these is that NEON isn't actually required in most
 if not all of the ARM CPU specs. I've specifically dealt with the
 Tegra 2, which is used in a lot of phones and has no NEON support even
 though it's ARM Cortex-A9.


 There's a official armv7-a ABI for android, it doesn't use 'hard', but
 at least 'softfp' instead of 'soft'.

 Just found the relevant documentation: See
 android-ndk-r7/docs/STANDALONE-TOOLCHAIN.html 4/ ABI Compatibility:
 ------------------------
 If you want to target the 'armeabi-v7a' ABI, you will need ensure that
 the following two flags are being used:

 =A0CFLAGS=3D'-march=3Darmv7-a -mfloat-abi=3Dsoftfp'

 If you want to use Neon instructions, you will need one more compiler
 flag:

 =A0CFLAGS=3D'-march=3Darmv7-a -mfloat-abi=3Dsoftfp -mfpu=3Dneon'

 Also, is is *required* to use the following linker flags that routes
 around a CPU bug in some Cortex-A8 implementations:

 =A0LDFLAGS=3D'-Wl,--fix-cortex-a8'
 ------------------------
 so according to those docs, you simply pass those flags to the
 compiler, no need to recompile the compiler.




From the ARM Neon Intrinisics page:


"These built-in intrinsics for the ARM Advanced SIMD extension are
available when the -mfpu=3Dneon switch is used."


--=20
Iain Buclaw

*(p < e ? p++ : p) =3D (c & 0x0f) + '0';



 Feb 06 2012



prev sibling  parent  Manu <turkeyman gmail.com>  writes:


On 6 February 2012 10:11, Johannes Pfau <nospam example.com> wrote:


 Am Mon, 6 Feb 2012 01:48:32 -0600
 schrieb Andrew Wiley <wiley.andrew.j gmail.com>:


 Actually, if the Android default is to build against softfloat ABI,
 you may be stuck with it. If Android doesn't require hardfloat to run
 and doesn't let developers provide multiple binaries for different
 platforms (which it might - I don't know), things get very hard.

 Also, with NEON, one of the things you don't really hear until you
 start working with these is that NEON isn't actually required in most
 if not all of the ARM CPU specs. I've specifically dealt with the
 Tegra 2, which is used in a lot of phones and has no NEON support even
 though it's ARM Cortex-A9.


 There's a official armv7-a ABI for android, it doesn't use 'hard', but
 at least 'softfp' instead of 'soft'.

 Just found the relevant documentation: See
 android-ndk-r7/docs/STANDALONE-TOOLCHAIN.html 4/ ABI Compatibility:
 ------------------------
 If you want to target the 'armeabi-v7a' ABI, you will need ensure that
 the following two flags are being used:

  CFLAGS='-march=armv7-a -mfloat-abi=softfp'

 If you want to use Neon instructions, you will need one more compiler
 flag:

  CFLAGS='-march=armv7-a -mfloat-abi=softfp -mfpu=neon'

 Also, is is *required* to use the following linker flags that routes
 around a CPU bug in some Cortex-A8 implementations:

  LDFLAGS='-Wl,--fix-cortex-a8'
 ------------------------
 so according to those docs, you simply pass those flags to the
 compiler, no need to recompile the compiler.


Sorry, missed this one. Did spot those flags in the build scripts, so yeah,
just missed them last night >_<
Sorry about that. I'll try again this evening and see how it looks.



 Feb 06 2012



prev sibling next sibling parent reply Andrew Wiley <wiley.andrew.j gmail.com>  writes:


On Mon, Feb 6, 2012 at 1:40 AM, Johannes Pfau <nospam example.com> wrote:

 Am Mon, 6 Feb 2012 03:07:31 +0200
 schrieb Manu <turkeyman gmail.com>:


 On 6 February 2012 02:25, Manu <turkeyman gmail.com> wrote:


 On 6 February 2012 00:04, Johannes Pfau <nospam example.com> wrote:


 Am Sun, 5 Feb 2012 18:04:12 +0100
 schrieb Johannes Pfau <nospam example.com>:


 I will probably need some more time to get this working...


 I have some good news:
 http://www.mediafire.com/?107we120sh3xx

 I fixed that problem and then the whole build worked fine. I'll
 post build instructions soon, but the binaries are ready. I only
 did a simple gdc -c test.d to check the compiler, but it seems to
 work.

 Linking against druntime fails, as it uses functions which are not
 available on Android (backtrace, signal stuff).

 I also built a simple hello world on linux (printf, no runtime)
 and ran it on my android phone, and it worked!

 In case you haven't used GDC without runtime before, a short
 introduction:

 * use gdc -nophoboslib to make gdc not link against phobos (and
 afaik, druntime)
 * theres also -nostdlib in case you need it

 * You'll get an error about a missing _Dmodule_ref symbol. That
 symbol is used by module constructors and not generated by gdc if
 =A0-nophoboslib was passed. As long as you don't run the module
 =A0constructors, you can add a fake _Dmodule_ref in a .c file:

 ------------
 void* _Dmodule_ref;
 ------------

 * The compiler defines version(Android)

 Here's my hello world:
 ------------
 version(Android)
 {
 =A0 =A0pragma(msg, "Hello Android!");
 }

 extern(C)
 {
 =A0 =A0int printf(in char* format, ...);
 }

 extern(C) void main()
 {
 =A0 =A0printf("Hello, %s!\n".ptr, "Android".ptr);
 }
 ------------

 compile the _Dmodule_ref into hack.o, then use
 gdc -nophoboslib hello.d hack.o


 Amazing! You sir, are a genius!
 I'm gonna have to have some fun with that after work tomorrow :)

 I reckon this binary distro should be put on d-p-l somewhere
 obvious.


 I just tried with -mfpu=3Dneon, which should allow GCC to generate neon
 opcodes for the simd stuff, but it didn't seem to want to do that. In
 fact it generates really horrible code where it CALLS an intrinsic
 for each float in the vector...
 Any idea why this wouldn't work out of the box?


 The android toolchain configures gcc with: +=3D --with-float=3Dsoft
 --with-fpu=3Dvfp --with-arch=3Darmv5te

 I could try to build an optimized build, but then you'll have to tell
 me what processor you're using. Cortex A8?

 I'm not sure if you can override that at runtime. You could probably
 try:
 -mfloat-abi=3Dhard -mcpu=3Dcortex-a8 -march=3Darmv7-a -mfpu=3Dneon


I'm pretty sure you have to rebuild the entire toolchain to switch
from softfloat to hardfloat.



 Feb 05 2012



  parent  Johannes Pfau <nospam example.com>  writes:


Am Mon, 6 Feb 2012 01:42:26 -0600
schrieb Andrew Wiley <wiley.andrew.j gmail.com>:


 
 I'm pretty sure you have to rebuild the entire toolchain to switch
 from softfloat to hardfloat.


I also thought that, but GCC docs say:
-with-fpu=type
--with-float=type
These configure options provide **default** values for the -mschedule=,
-march=, -mtune=, -mabi=, and -mfpu= options and for -mhard-float or
-msoft-float. As with --with-cpu, which switches will be accepted and
acceptable values of the arguments depend on the target.

That also matches the Android NDK documentation.



 Feb 06 2012



prev sibling  parent  Manu <turkeyman gmail.com>  writes:


On 6 February 2012 09:40, Johannes Pfau <nospam example.com> wrote:


 Am Mon, 6 Feb 2012 03:07:31 +0200
 schrieb Manu <turkeyman gmail.com>:


 On 6 February 2012 02:25, Manu <turkeyman gmail.com> wrote:


 On 6 February 2012 00:04, Johannes Pfau <nospam example.com> wrote:


 Am Sun, 5 Feb 2012 18:04:12 +0100
 schrieb Johannes Pfau <nospam example.com>:


 I will probably need some more time to get this working...


 I have some good news:
 http://www.mediafire.com/?107we120sh3xx

 I fixed that problem and then the whole build worked fine. I'll
 post build instructions soon, but the binaries are ready. I only
 did a simple gdc -c test.d to check the compiler, but it seems to
 work.

 Linking against druntime fails, as it uses functions which are not
 available on Android (backtrace, signal stuff).

 I also built a simple hello world on linux (printf, no runtime)
 and ran it on my android phone, and it worked!

 In case you haven't used GDC without runtime before, a short
 introduction:

 * use gdc -nophoboslib to make gdc not link against phobos (and
 afaik, druntime)
 * theres also -nostdlib in case you need it

 * You'll get an error about a missing _Dmodule_ref symbol. That
 symbol is used by module constructors and not generated by gdc if
  -nophoboslib was passed. As long as you don't run the module
  constructors, you can add a fake _Dmodule_ref in a .c file:

 ------------
 void* _Dmodule_ref;
 ------------

 * The compiler defines version(Android)

 Here's my hello world:
 ------------
 version(Android)
 {
    pragma(msg, "Hello Android!");
 }

 extern(C)
 {
    int printf(in char* format, ...);
 }

 extern(C) void main()
 {
    printf("Hello, %s!\n".ptr, "Android".ptr);
 }
 ------------

 compile the _Dmodule_ref into hack.o, then use
 gdc -nophoboslib hello.d hack.o


 Amazing! You sir, are a genius!
 I'm gonna have to have some fun with that after work tomorrow :)

 I reckon this binary distro should be put on d-p-l somewhere
 obvious.


 I just tried with -mfpu=neon, which should allow GCC to generate neon
 opcodes for the simd stuff, but it didn't seem to want to do that. In
 fact it generates really horrible code where it CALLS an intrinsic
 for each float in the vector...
 Any idea why this wouldn't work out of the box?


 The android toolchain configures gcc with: += --with-float=soft
 --with-fpu=vfp --with-arch=armv5te

 I could try to build an optimized build, but then you'll have to tell
 me what processor you're using. Cortex A8?

 I'm not sure if you can override that at runtime. You could probably
 try:
 -mfloat-abi=hard -mcpu=cortex-a8 -march=armv7-a -mfpu=neon


That's interesting. I seem to recall in a recent NDK noticing that they had
changed to armv7 by default... but looking at the R6 NDK, it looks like
it's configured basically identical to your toolchain.
I must just be missing a whole function of compile options, but I can't see
any option in the standard build scripts to enable hardware fpu :/
The options I see that are supplied are: -ffast-math -mfloat-abi=softfp
-march=armv7-a

I imagine all android 2+ devices have at least armv7's with a hardware
fpu...

Interesting that NEON is not supported on all hardware. Annoying to do
runtime detection to take advantage of stuff like that >_<



 I wanted to add ARM support to my std.simd work here as a better
 proof of concept.

 Iain: was there anything particularly special you needed to do to
 hook the x86 SSE stuff to GDC which would need to be duplicated for
 ARM? gcc.builtins doesn't seen to have any ARM intrinsics in there
 either...







 Feb 06 2012



prev sibling  parent  Iain Buclaw <ibuclaw ubuntu.com>  writes:


On 6 February 2012 01:07, Manu <turkeyman gmail.com> wrote:

 On 6 February 2012 02:25, Manu <turkeyman gmail.com> wrote:

 On 6 February 2012 00:04, Johannes Pfau <nospam example.com> wrote:

 Am Sun, 5 Feb 2012 18:04:12 +0100
 schrieb Johannes Pfau <nospam example.com>:


 I will probably need some more time to get this working...


 I have some good news:
 http://www.mediafire.com/?107we120sh3xx

 I fixed that problem and then the whole build worked fine. I'll post
 build instructions soon, but the binaries are ready. I only did a
 simple gdc -c test.d to check the compiler, but it seems to work.

 Linking against druntime fails, as it uses functions which are not
 available on Android (backtrace, signal stuff).

 I also built a simple hello world on linux (printf, no runtime) and ran
 it on my android phone, and it worked!

 In case you haven't used GDC without runtime before, a short
 introduction:

 * use gdc -nophoboslib to make gdc not link against phobos (and afaik,
 =A0druntime)
 * theres also -nostdlib in case you need it

 * You'll get an error about a missing _Dmodule_ref symbol. That symbol
 =A0is used by module constructors and not generated by gdc if
 =A0-nophoboslib was passed. As long as you don't run the module
 =A0constructors, you can add a fake _Dmodule_ref in a .c file:

 ------------
 void* _Dmodule_ref;
 ------------

 * The compiler defines version(Android)

 Here's my hello world:
 ------------
 version(Android)
 {
 =A0 =A0pragma(msg, "Hello Android!");
 }

 extern(C)
 {
 =A0 =A0int printf(in char* format, ...);
 }

 extern(C) void main()
 {
 =A0 =A0printf("Hello, %s!\n".ptr, "Android".ptr);
 }
 ------------

 compile the _Dmodule_ref into hack.o, then use
 gdc -nophoboslib hello.d hack.o



 Amazing! You sir, are a genius!
 I'm gonna have to have some fun with that after work tomorrow :)

 I reckon this binary distro should be put on d-p-l somewhere obvious.



 I just tried with -mfpu=3Dneon, which should allow GCC to generate neon
 opcodes for the simd stuff, but it didn't seem to want to do that. In fac=


t

 it generates really horrible code where it CALLS an intrinsic for each fl=


oat

 in the vector...
 Any idea why this wouldn't work out of the box?

 I wanted to add ARM support to my std.simd work here as a better proof of
 concept.

 Iain: was there anything particularly special you needed to do to hook th=


e

 x86 SSE stuff to GDC which would need to be duplicated for ARM? gcc.built=


ins

 doesn't seen to have any ARM intrinsics in there either...


Nope - its all arch agnostic.  Just requires that:
a) The target you are building for has the functions available
b) The functions in question can be represented using D types.


--=20
Iain Buclaw

*(p < e ? p++ : p) =3D (c & 0x0f) + '0';



 Feb 06 2012



prev sibling  parent reply =?ISO-8859-1?Q?S=F6nke_Ludwig?= <ludwig informatik.uni-luebeck.de>  writes:


Great thing! I tried some time ago to build gdc like this, but I always 
faild miserably due to obscure make problems. Maybe my library versions 
were slightly off... I'll try this out later today.



 Feb 05 2012



  parent  Johannes Pfau <nospam example.com>  writes:


Am Sun, 05 Feb 2012 12:21:43 +0100
schrieb S=C3=B6nke Ludwig <ludwig informatik.uni-luebeck.de>:


 Great thing! I tried some time ago to build gdc like this, but I
 always faild miserably due to obscure make problems. Maybe my library
 versions were slightly off... I'll try this out later today.


Library versions are one problem but I also had build
failures when texinfo wasn't installed (although all packages say
texinfo is completely optional...). The hardest part was actually
getting a plain gcc-4.6.2 toolchain to build, adding gdc is easy.



 Feb 05 2012