x32-abi with D?

I was planning to install FreeBSD, but I was wondering if x32-abi(i.e. x86-64 but using fast 32bit pointers) is a supported configuration together with D in linux using the D gnu compiler, then it would be the incentive to go linux instead. if not supported, is it planned to be supported?

On 26 May 2012 11:00, Franz <franz.sass@gmx.de> wrote: > I was planning to install FreeBSD, but I was wondering if x32-abi(i.e. x86-64 but using fast 32bit pointers) is a supported configuration together with D in linux using the D gnu compiler, then it would be the incentive to go linux instead. > > if not supported, is it planned to be supported? > The compiler is able to cope. Have made some updates to the D runtime and Phobos library to weed out any issues relating to such platforms (NaCL is another system which uses 32bit pointers on x86_64 arch), though I'm not aware of the current working state. Regards -- Iain Buclaw *(p < e ? p++ : p) = (c & 0x0f) + '0';

> The compiler is able to cope. Have made some updates to the D runtime > and Phobos library to weed out any issues relating to such platforms > (NaCL is another system which uses 32bit pointers on x86_64 arch), Should go into upstream druntime shouldn't it?

On 26-05-2012 14:03, Trass3r wrote: >> The compiler is able to cope. Have made some updates to the D runtime >> and Phobos library to weed out any issues relating to such platforms >> (NaCL is another system which uses 32bit pointers on x86_64 arch), > > Should go into upstream druntime shouldn't it? No, druntime is compiler-specific. Phobos is a different story. -- Alex Rønne Petersen alex@lycus.org http://lycus.org

On 26-05-2012 14:06, Alex Rønne Petersen wrote: > On 26-05-2012 14:03, Trass3r wrote: >>> The compiler is able to cope. Have made some updates to the D runtime >>> and Phobos library to weed out any issues relating to such platforms >>> (NaCL is another system which uses 32bit pointers on x86_64 arch), >> >> Should go into upstream druntime shouldn't it? > > No, druntime is compiler-specific. Phobos is a different story. > Speaking of which, Iain, any way we could upstream all of GDC's Phobos changes? (Perhaps same way you did it with DMD?) -- Alex Rønne Petersen alex@lycus.org http://lycus.org

On 26 May 2012 13:59, Alex Rønne Petersen <alex@lycus.org> wrote: > On 26-05-2012 14:06, Alex Rønne Petersen wrote: >> >> On 26-05-2012 14:03, Trass3r wrote: >>>> >>>> The compiler is able to cope. Have made some updates to the D runtime and Phobos library to weed out any issues relating to such platforms (NaCL is another system which uses 32bit pointers on x86_64 arch), >>> >>> >>> Should go into upstream druntime shouldn't it? >> >> >> No, druntime is compiler-specific. Phobos is a different story. >> > > Speaking of which, Iain, any way we could upstream all of GDC's Phobos changes? (Perhaps same way you did it with DMD?) > > You could try, but I can't think of any changes that would be considered suitable for upstreaming. To list notable differences off the top of my head: - void* is replaced with va_list where appropriate. - some version code to whom's identifiers are only emitted from the gdc compiler. - some functions in std.math call the long double rather than double math lib functions. - std.format.doFormat has some difference for consideration that the va_list varies on differing architectures. -- Iain Buclaw *(p < e ? p++ : p) = (c & 0x0f) + '0';