Good day.
Would like to ask a question to the developers of the language:
Is the development of a compiler D under the ARM or is at least
in the plans?
On Tue, 28 Aug 2012 05:27:23 -0500, Shadow_exe wrote:
Good day.
Would like to ask a question to the developers of the language:
Is the development of a compiler D under the ARM or is at least in the
plans?
The D specification states that 16bit or below will not be supported.
DMD is a nogo
On Tuesday, 28 August 2012 at 10:53:17 UTC, 1100110 wrote:
On Tue, 28 Aug 2012 05:27:23 -0500, Shadow_exe
wrote:
The D specification states that 16bit or below will not be
supported.
DMD is a nogo for ARM right now, so take a look at LDC or GDC
But I think the ARM main processors are all
On Tue, 28 Aug 2012 06:23:11 -0500, MattCoder
wrote:
On Tuesday, 28 August 2012 at 10:53:17 UTC, 1100110 wrote:
On Tue, 28 Aug 2012 05:27:23 -0500, Shadow_exe
wrote:
The D specification states that 16bit or below will not be supported.
DMD is a nogo for ARM right now, so take a look at
On Tue, 28 Aug 2012 06:23:11 -0500, MattCoder
wrote:
On Tuesday, 28 August 2012 at 10:53:17 UTC, 1100110 wrote:
On Tue, 28 Aug 2012 05:27:23 -0500, Shadow_exe
wrote:
The D specification states that 16bit or below will not be supported.
DMD is a nogo for ARM right now, so take a look at
Al 28/08/12 12:27, En/na Shadow_exe ha escrit:
> Good day.
> Would like to ask a question to the developers of the language:
> Is the development of a compiler D under the ARM or is at least in the plans?
>
GDC and LDC are both available for ARM processors on the last Debian s
I know, I know, this question has been asked many times before.
But it came up in a meeting the other day: is there any work
being done on making D an ARM citizen so that _non-trivial_ D
code can be ported to smartphones and the like? If so, what it
the rough time frame?
Hello,
I'm developing embedded system product on ARM9/Linux platform and I wish
I could use D and vibe.d for this task.
I have couple of questions in this matter:
- What is the current status of ARM support?
- Does GDC support cross-compiling to ARM?
- Is it possible to remote-debug D co
So it seems that ARM is going to be getting quite a bit bigger in the
future, between the rise of smarter phones and Windows 8 support, and in
general D just doesn't exist on ARM.
GDC kind of works, but I've been unable to come up with a simple test case
for a bug with the secti
Hello, is there a chance an ARM backend can be written for dmd this
year? I realize this question has been asked periodically going back
4-5 years, but ARM is turning into a major platform and I feel D2 could
do very well in this market, particularly with the renewed emphasis on
mobile
On Thursday, 14 November 2013 at 14:47:47 UTC, Chris wrote:
I know, I know, this question has been asked many times before.
But it came up in a meeting the other day: is there any work
being done on making D an ARM citizen so that _non-trivial_ D
code can be ported to smartphones and the like
On Thursday, 14 November 2013 at 15:31:25 UTC, eles wrote:
On Thursday, 14 November 2013 at 14:47:47 UTC, Chris wrote:
I know, I know, this question has been asked many times
before. But it came up in a meeting the other day: is there
any work being done on making D an ARM citizen so that
On Thursday, 14 November 2013 at 14:47:47 UTC, Chris wrote:
I know, I know, this question has been asked many times before.
But it came up in a meeting the other day: is there any work
being done on making D an ARM citizen so that _non-trivial_ D
code can be ported to smartphones and the like
On Thursday, 14 November 2013 at 16:14:16 UTC, Kai Nacke wrote:
On Thursday, 14 November 2013 at 14:47:47 UTC, Chris wrote:
I know, I know, this question has been asked many times
before. But it came up in a meeting the other day: is there
any work being done on making D an ARM citizen so that
On 2013-11-14 17:21, Chris wrote:
Thanks for your reply, Kai. That's good news, however iOS and Android
support is crucial. I hope D can soon be ported to ARM, it's just too
important.
If you want to do anything useful on iOS you need to use Objective-C
libraries, for that you bas
On 15 November 2013 05:14, Jacob Carlborg wrote:
> On 2013-11-14 17:21, Chris wrote:
>
> Thanks for your reply, Kai. That's good news, however iOS and Android
>> support is crucial. I hope D can soon be ported to ARM, it's just too
>> important.
>>
>
&g
On 11/14/2013 05:14 PM, Kai Nacke wrote:
But this is only half of the story. My target is Linux/ARM which is
already supported by druntime/phobos. If you target a smartphone then
you also have to add Android or iOS support to druntime/phobos.
Currently version (linux) in druntime is equivalent
On 2013-11-14 19:14:03 +, Jacob Carlborg said:
On 2013-11-14 17:21, Chris wrote:
Thanks for your reply, Kai. That's good news, however iOS and Android
support is crucial. I hope D can soon be ported to ARM, it's just too
important.
If you want to do anything useful on iOS y
On Friday, 15 November 2013 at 00:18:50 UTC, Martin Nowak wrote:
On 11/14/2013 05:14 PM, Kai Nacke wrote:
But this is only half of the story. My target is Linux/ARM
which is
already supported by druntime/phobos. If you target a
smartphone then
you also have to add Android or iOS support to
On Friday, 15 November 2013 at 06:18:00 UTC, Joakim wrote:
On Friday, 15 November 2013 at 00:18:50 UTC, Martin Nowak wrote:
On 11/14/2013 05:14 PM, Kai Nacke wrote:
But this is only half of the story. My target is Linux/ARM
which is
already supported by druntime/phobos. If you target a
On 2013-11-15 00:35, Manu wrote:
Very good point. I wonder if there's room to make a push for this in 2.065.
Highly unlikely. It seems like Walter wanted us to first implement ARC,
to not be worse the Objective-C currently is. But we haven't been able
to come to an agreement on how to do th
the last time I announced it.
And since the DMD backend won't emit ARM code, if I were still working
on this the first thing I'd do is rebase everything to work on top of LDC.
I think that would be quite difficult. Although it would probably be
easier to get 64bit and modern runt
On Friday, 15 November 2013 at 07:22:07 UTC, Paulo Pinto wrote:
On Friday, 15 November 2013 at 06:18:00 UTC, Joakim wrote:
As Kai says, has anyone worked on getting D running on Android
before? I've been thinking about attempting an Android port
for years. I thought I'd spin up some x86 VMs t
ch/android
Anyone get any farther than that?
Would it make sense to use dmd for linux/x86 to cross-compile
to Android/x86 or is this a job for ldc/gdc only?
I would say ldc/gdc only, as LLVM/gcc are the supported NDK
toolchains and dmd lacks an ARM backend.
NDK
toolchains and dmd lacks an ARM backend.
Yeah, I'm aware of these facts, but I don't think they matter.
For one, dmd not having an ARM backend doesn't impact me since
I'm targeting Android/x86 for now, :) as stated earlier. I don't
think it's relevant what
?
I would say ldc/gdc only, as LLVM/gcc are the supported NDK
toolchains and dmd lacks an ARM backend.
Yeah, I'm aware of these facts, but I don't think they matter.
For one, dmd not having an ARM backend doesn't impact me since
I'm targeting Android/x86 for now, :) a
gt; Would it make sense to use dmd for linux/x86 to cross-compile to
>>>> Android/x86 or is this a job for ldc/gdc only?
>>>>
>>>
>>> I would say ldc/gdc only, as LLVM/gcc are the supported NDK toolchains
>>> and dmd lacks an ARM backend.
>>
On 2013-11-15 10:45, Paulo Pinto wrote:
As far as I know dmd does not support cross compiling.
Only for 32bit/64bit on the same architecture.
--
/Jacob Carlborg
On 2013-11-15 00:35, Manu wrote:
Very good point. I wonder if there's room to make a push for this in 2.065.
Note, I'm willing work on to syncing my branches to upstream if Walter
is interested in this. Getting support for 64bit and modern runtime
would be too far away for this release.
--
On Friday, 15 November 2013 at 06:18:00 UTC, Joakim wrote:
On Friday, 15 November 2013 at 00:18:50 UTC, Martin Nowak wrote:
On 11/14/2013 05:14 PM, Kai Nacke wrote:
But this is only half of the story. My target is Linux/ARM
which is
already supported by druntime/phobos. If you target a
On Friday, 15 November 2013 at 09:45:42 UTC, Paulo Pinto wrote:
As far as I know dmd does not support cross compiling.
I started skimming the dmd source to see how it handled porting
to new platforms and I found the following:
* Linux Version
* -
* There are two main issues: hos
Thanks for all your answers. I see that it's still a big big
issue. I believe we really have to push this, because ARM support
is vital. If we want people to use D, there will have to be a
port to ARM, else it will put people off. The code I've been
working on runs fine on Windows
On Friday, 15 November 2013 at 09:20:18 UTC, Joakim wrote:
For one, dmd not having an ARM backend doesn't impact me since
I'm targeting Android/x86 for now, :) as stated earlier.
Interesting, then you'll mostly focus on druntime and glibc vs.
bionic issues.
The linux/ELF
On Friday, 15 November 2013 at 11:46:29 UTC, Chris wrote:
I see that it's still a big big issue.
It's not that much effort. Build gdc for ARM and fix druntime.
I believe we really have to push this, because ARM support is
vital.
Well somebody has to do it, so if you have so much i
re is a some support, but not too much. The existence of
the TARGET_* macros means that you can't have one compiler with 2
or more platform targets.
But there should be no real problem to create a dmd executable on
Linux/ARM producing object files for Windows/x86. (Well - no
problem exce
Bionic even got
[dl_iterate_phdr](https://github.com/android/platform_bionic/commit/24053a461e7a20f34002262c1bb122023134989)
which we need for shared library support.
Write me a mail if you hit any druntime issues during the port.
On 2013-11-15 07:26:56 +, Jacob Carlborg said:
On 2013-11-15 00:35, Manu wrote:
Very good point. I wonder if there's room to make a push for this in 2.065.
Highly unlikely. It seems like Walter wanted us to first implement
ARC, to not be worse the Objective-C currently is. But we have
On 2013-11-15 07:33:40 +, Jacob Carlborg said:
On 2013-11-15 02:50, Michel Fortin wrote:
And since the DMD backend won't emit ARM code, if I were still working
on this the first thing I'd do is rebase everything to work on top of LDC.
I think that would be quite difficult. A
On 2013-11-15 13:42, Michel Fortin wrote:
Honestly, what I'd do is implement ARC for Objective-C types in the
compiler without waiting for Walter to decide on anything. There's
almost nothing to decide when it comes to how D/Objective-C does it: you
have to do it the same way as clang. And you c
On 2013-11-15 13:41, Michel Fortin wrote:
That was my idea too initially: put it in the reference implementation
and other implementations will follow, and it'll become part of the
language. That'd be great. But it's hard when you have to fix the
backend to emit what you need. I have some fears
On 2013-11-15 12:53:18 +, Jacob Carlborg said:
On 2013-11-15 13:42, Michel Fortin wrote:
Honestly, what I'd do is implement ARC for Objective-C types in the
compiler without waiting for Walter to decide on anything. There's
almost nothing to decide when it comes to how D/Objective-C does
On 2013-11-15 14:38, Michel Fortin wrote:
You mean if Walter would accept D/Objective-C without ARC? No idea. Ask
him, or submit a pull request just to gauge the reaction.
No, I was referring to just implementing ARC like it's done in Objective-C.
People have been manually managing memory wi
On 2013-11-15 14:02:20 +, Jacob Carlborg said:
On 2013-11-15 14:38, Michel Fortin wrote:
You mean if Walter would accept D/Objective-C without ARC? No idea. Ask
him, or submit a pull request just to gauge the reaction.
No, I was referring to just implementing ARC like it's done in Objec
On Friday, 15 November 2013 at 12:07:19 UTC, Martin Nowak wrote:
On Friday, 15 November 2013 at 09:20:18 UTC, Joakim wrote:
For one, dmd not having an ARM backend doesn't impact me since
I'm targeting Android/x86 for now, :) as stated earlier.
Interesting, then you'll mostly fo
On 15 November 2013 18:40, Joakim wrote:
> On Friday, 15 November 2013 at 12:07:19 UTC, Martin Nowak wrote:
>
>> On Friday, 15 November 2013 at 09:20:18 UTC, Joakim wrote:
>>
>>> For one, dmd not having an ARM backend doesn't impact me since I'm
>>&g
Am Fri, 15 Nov 2013 09:24:53 +0100
schrieb "Joakim" :
> On Friday, 15 November 2013 at 07:22:07 UTC, Paulo Pinto wrote:
> > On Friday, 15 November 2013 at 06:18:00 UTC, Joakim wrote:
> >> As Kai says, has anyone worked on getting D running on Android
> >> before? I've been thinking about attempt
On Friday, 15 November 2013 at 18:44:20 UTC, Iain Buclaw wrote:
On 15 November 2013 18:40, Joakim wrote:
Yes, I thought that would be easier, to split the effort into
two parts.
First, get D working on Android/x86, then, linux/ARM. Some
fine day, we
combine the two into Android/ARM
On 15 November 2013 21:14, Joakim wrote:
> On Friday, 15 November 2013 at 18:44:20 UTC, Iain Buclaw wrote:
>
>> On 15 November 2013 18:40, Joakim wrote:
>>
>>> Yes, I thought that would be easier, to split the effort into two parts.
>>> First, get D wor
A few weeks ago I tried compiling gdc and ldc on my Debian arm
system and they built Ok but the apps crashed when run. I think
the error was something to do with fibres in Phobos and druntime.
I tried quickly hacking in missing architecture macros for Arm
but I didn't know what I was doi
On 11/16/2013 06:51 PM, Andrew wrote:
I think the error was something to do with fibres in Phobos and druntime.
Fibers probably won't work out of the box, but they aren't used anywhere
in druntime/phobos so did you get a hello world to run?
On Saturday, 16 November 2013 at 18:03:29 UTC, Martin Nowak wrote:
On 11/16/2013 06:51 PM, Andrew wrote:
I think the error was something to do with fibres in Phobos
and druntime.
Fibers probably won't work out of the box, but they aren't used
anywhere in druntime/phobos so did you get a hello
Just a thought but most ARM systems, Linux based, used EABI
whereas iOS uses an Apple specific ABI so you'll probably need to
target each separately. Also there are two variants of EABI
hard-float (most common now) and soft-float.
1. Remove the stupid GC, it doesn't scale anyway
2. Compile to C or C++
DONE!
WAHOOO
On Friday, 15 November 2013 at 19:09:24 UTC, Johannes Pfau wrote:
* The main program in Android should always be java code,
native code
loaded as shared libraries. This is implemented in DMD now,
but not
in GDC. (And IIRC not in LDC either?)
On the 2.064 frontend branch, LDC already uses
On Friday, 15 November 2013 at 10:31:40 UTC, Elvis Zhou wrote:
On Friday, 15 November 2013 at 06:18:00 UTC, Joakim wrote:
Also, does dmd have any support for cross-compilation or is it
better to stick to ldc/gdc when cross compiling to Android?
A month ago I tried to cross compile a Hello Worl
l the Android llvm/clang patches and
there's little of significance. They hardcode two clang options
for android/x86, -mstackrealign and -msse3, add a few tweaks for
ARM, and that's about it. Most of the patches are for some other
NDK work by MediaTek, which don't appear to be u
BI is not that different from linux.
Alright, went through all the Android llvm/clang patches and
there's little of significance. They hardcode two clang
options for android/x86, -mstackrealign and -msse3, add a few
tweaks for ARM, and that's about it. Most of the patches are
for some
On Monday, 25 November 2013 at 11:32:56 UTC, Chris wrote:
On Monday, 25 November 2013 at 10:38:24 UTC, Joakim wrote:
Next step, get dmd to do the same with a "hello world" native
Android app. I'll update this thread as I go, for anyone
who's interested.
Thanks, I'm interested.
I just spent a
On Monday, 25 November 2013 at 22:32:26 UTC, Joakim wrote:
On Monday, 25 November 2013 at 11:32:56 UTC, Chris wrote:
On Monday, 25 November 2013 at 10:38:24 UTC, Joakim wrote:
Next step, get dmd to do the same with a "hello world" native
Android app. I'll update this thread as I go, for anyone
On Tuesday, 26 November 2013 at 09:53:07 UTC, Chris wrote:
On Monday, 25 November 2013 at 22:32:26 UTC, Joakim wrote:
Next, getting this minimal app running on Android/x86. It
turns out there is some support for building executables
directly in the Android NDK, just undocumented, though the
d
On Tuesday, 26 November 2013 at 11:22:59 UTC, Joakim wrote:
That is what the docs say if you want to build a native Android
app, presumably that you distribute through the Play Store.
But you can always build a native app for your own local dev
build of Android, at least for porting purposes.
apps are working, just not officially supported. I actually had
a native Hello World working on ARM/Android with GDC, however fixing
bugs related to native apps usually isn't high priority on Android.
This bug for example wasn't fixed back then and was a showstopper:
http://code.goog
On Tuesday, 26 November 2013 at 17:12:38 UTC, Johannes Pfau wrote:
Native apps are working, just not officially supported. I
actually had
a native Hello World working on ARM/Android with GDC, however
fixing
bugs related to native apps usually isn't high priority on
Android.
This bu
On Tuesday, 26 November 2013 at 11:22:59 UTC, Joakim wrote:
What JNI-D stuff have you tried and on what platform,
linux/x86? I'll try the shared library approach on Android at
some point and report back.
If I remember correctly, I did something like this (think it was
on OS X):
1. Create
On Wednesday, 27 November 2013 at 13:52:17 UTC, Chris wrote:
On Tuesday, 26 November 2013 at 11:22:59 UTC, Joakim wrote:
What JNI-D stuff have you tried and on what platform,
linux/x86? I'll try the shared library approach on Android at
some point and report back.
If I remember correctly,
Alright, submitted my first pull request for Android support in
druntime:
https://github.com/D-Programming-Language/druntime/pull/681
I'll push all further changes to druntime in my android branch:
https://github.com/joakim-noah/druntime/tree/android
Hopefully, I can get some subset of D work
On 01.12.2013 14:30, Joakim wrote:
//test.d
import core.stdc.stdio;
extern (C) int main() { fputs("doing this for real?", stderr); return 0;}
It doesn't link on Win32, Win64, or Android. It works on linux and
FreeBSD. Here's the output on platforms where it doesn't work:
The reason this d
On Monday, 2 December 2013 at 08:25:39 UTC, Rainer Schuetze wrote:
On 01.12.2013 14:30, Joakim wrote:
//test.d
import core.stdc.stdio;
extern (C) int main() { fputs("doing this for real?", stderr);
return 0;}
It doesn't link on Win32, Win64, or Android. It works on
linux and
FreeBSD. H
On 02.12.2013 10:36, Joakim wrote:
On Monday, 2 December 2013 at 08:25:39 UTC, Rainer Schuetze wrote:
On 01.12.2013 14:30, Joakim wrote:
//test.d
import core.stdc.stdio;
extern (C) int main() { fputs("doing this for real?", stderr); return
0;}
It doesn't link on Win32, Win64, or Android.
Yes, ARM D support is really important.
https://josephscott.org/archives/2013/12/is-facebook-planning-a-move-to-arm-based-servers/
BTW, it might be a good idea to also target ARM64, while we're at
it...
On Friday, 13 December 2013 at 17:18:30 UTC, Luís Marques wrote:
Yes, ARM D support is really important.
https://josephscott.org/archives/2013/12/is-facebook-planning-a-move-to-arm-based-servers/
It also came out today that Google is thinking about designing
custom ARM chips to put in their
On Dec 13, 2013 8:40 PM, "Joakim" wrote:
>
> On Friday, 13 December 2013 at 17:18:30 UTC, Luís Marques wrote:
>>
>> Yes, ARM D support is really important.
>>
>>
https://josephscott.org/archives/2013/12/is-facebook-planning-a-move-to-arm-based-servers/
>
On Monday, 2 December 2013 at 18:35:36 UTC, Rainer Schuetze wrote:
On 02.12.2013 10:36, Joakim wrote:
Where is this "implicit include directive?" It's confusing
because "dmd
-v" shows the exact same linker command being run whether that
"extern
(C)" is there before main or not.
The compiler
I just got a basic D program running with a patched druntime on
Android/x86. :) I was also able to compile and run sieve.d from
the D samples, after replacing std.stdio.writefln with
core.stdc.stdio.printf and moving the flags declaration inside
main. It would segfault at "flags[]=true" if I d
ified to answer these questions, but I offer
my perceptions anyway.
I'm working on a bare-metal ARM Cortex-M port, which I believe is
quite different from what you are looking for. What exactly is
your hardware? RaspberryPi? BeagleBone? Android Tablet?
I have couple of questions in th
D on ARMv7,
not a core developer, but I'll take a shot at answering your
questions.
- What is the current status of ARM support?
Limited. The reference DMD compiler has no support for ARM,
while the LDC and GDC compilers are trying to utilize the ARM
backends of llvm and gcc to add
On Friday, 10 January 2014 at 08:27:39 UTC, Joakim wrote:
On Thursday, 9 January 2014 at 18:07:16 UTC, Piotr Szturmaj
wrote:
- Does druntime support ARM plaforms?
Grepping through the code, druntime appears to use a fair
amount of x86 assembly, but I have not yet looked into how much
of that
There were people trying vibe.d on ARM/Linux here and there with
several issues that may or may not be already fixed by
LDC/GDC/vibe.d developers. One thread I have found:
http://forum.rejectedsoftware.com/groups/rejectedsoftware.vibed/thread/6048/
As far as I know it works in general but
Am Fri, 10 Jan 2014 08:59:56 +
schrieb "Dicebot" :
> There were people trying vibe.d on ARM/Linux here and there with
> several issues that may or may not be already fixed by
> LDC/GDC/vibe.d developers. One thread I have found:
>
> http://forum.re
ask.
> >
> > I have couple of questions in this matter:
> Like Mike, I'm an interested user, who wants to see D on ARMv7,
> not a core developer, but I'll take a shot at answering your
> questions.
>
> > - What is the current status of ARM support?
>
rk
as well but is untested.
> I have couple of questions in this matter:
> - What is the current status of ARM support?
GDC is almost ready ready for a public beta.
Tested with Softfloat(no FPU)/Hardfloat on ARMv5/ARMv6:
* Compiler test suite passes as well as x86
* Druntime unittests p
On Sunday, 12 January 2014 at 11:31:07 UTC, Johannes Pfau wrote:
Am Fri, 10 Jan 2014 08:27:37 +
schrieb "Joakim" :
> - Does druntime support ARM plaforms?
Grepping through the code, druntime appears to use a fair
amount of x86 assembly, but I have not yet looked into how
mu
hould work
as well but is untested.
It's ARM926EJ-S CPU (ARMv5).
I have couple of questions in this matter:
- Can you estimate eventual cost of supporting D on ARM (think of
paid bounty).
Can't speak for anyone else but for me it's more a matter of missing
time than of money. Proba
ct on ARM9/Linux platform and I
>>> wish I could use D and vibe.d for this task.
>>>
>>
>> ARMv5 or ARMv4? I tested ARMv5 and that should work. ARMv4 should work
>> as well but is untested.
>
>
> It's ARM926EJ-S CPU (ARMv5).
>
>&
Iain Buclaw wrote:
QEMU testing is quirky. If your lucky and get it working, don't make
any system changes. :o)
What do you mean exactly?
Saying that, ARM is the only emulation that I've gotten working where
I've actually built GDC ontop of.
For anyone interested:
He
Am Mon, 13 Jan 2014 12:25:17 +0100
schrieb Piotr Szturmaj :
> Iain Buclaw wrote:
> > QEMU testing is quirky. If your lucky and get it working, don't
> > make any system changes. :o)
>
> What do you mean exactly?
>
> > Saying that, ARM is the only emulation
to run the auto-tester on. I don't care if I'm
logging into a virtual or physical box, as long as it supports ssh and the other requirements of the
test system.
I've used both in the past. On modern arm, I suspect it'd be significantly faster than even a very
fast x86 box e
Johannes Pfau wrote:
Am Mon, 13 Jan 2014 12:25:17 +0100
schrieb Piotr Szturmaj :
Iain Buclaw wrote:
QEMU testing is quirky. If your lucky and get it working, don't
make any system changes. :o)
What do you mean exactly?
Saying that, ARM is the only emulation that I've gotten wor
don't
>>>> make any system changes. :o)
>>>
>>>
>>> What do you mean exactly?
>>>
>>>> Saying that, ARM is the only emulation that I've gotten working
>>>> where I've actually built GDC ontop of.
>>>
>
actly?
Saying that, ARM is the only emulation that I've gotten working
where I've actually built GDC ontop of.
For anyone interested:
Here are prebuilt Debian Squeeze(2.6.32) / Wheezy(3.2.0) images for
Versatile/QEMU: http://people.debian.org/~aurel32/qemu/armel/ (link
On 2013-12-28 23:21, Joakim wrote:
I haven't completely grasped TLS and how it's done on OS X yet, but I
get the sense I'll have to modify dmd a little to get TLS working with
bionic. It appears that Martin and Johannes have looked into this
before, so if you two have any feedback, let me know.
Now is the time when ARM may become really important:
http://arstechnica.com/information-technology/2014/01/amd-reveals-its-first-arm-processor-8-core-opteron-a1100/
On Saturday, 28 December 2013 at 22:21:46 UTC, Joakim wrote:
I finished porting most of druntime to Android/x86 and have
started trying to run the tests: I just got 31 out of 38
druntime modules' unit tests to pass. :)
I figured out the segfault mentioned above was because TLS is
done differe
On Friday, 21 March 2014 at 19:59:41 UTC, Joakim wrote:
Been awhile since I updated on the Android effort: I'm now able
to get all 38 druntime modules' unit tests to pass on
Android/x86... under somewhat random conditions. It's finicky
and some of the tests start failing and many segfaulting o
On Thursday, 14 November 2013 at 14:47:47 UTC, Chris wrote:
I know, I know, this question has been asked many times before.
But it came up in a meeting the other day: is there any work
being done on making D an ARM citizen so that _non-trivial_ D
code can be ported to smartphones and the like
On 23/04/14 13:39, Joakim wrote:
Alright, finally hacked dmd to produce something like packed TLS for
ELF. I just ran the druntime unit tests on Android/x86 and all 38
modules passed, :) even after changing the number of TLS variables a
couple times, which was causing segfaults with the native
Hi guys!!!
I'm very intrested to use D. Tryed to code some simple programs
for Linux. But now I'm trying to make some ARM embedded solutions.
The main language for this point is C. All involved corporations,
which research compilers for embedded ARM stuff support C.
How do you t
First please see, for example, this ARM CPU
http://img.deusm.com/eetimes/AMD01.png
L1 cache per 1 core.
L2 cache per 2 cores.
L3 cache for all (8) cores.
It is critical for multithread BLAS (and D BLAS is going to be
the best BLAS ever) to estimate that L2 cache is per 2 cores.
In the same
The frexp test fails on ARM. I think the mask in line 1491 is
wrong:
https://github.com/D-Programming-Language/phobos/blob/master/std/math.d#L1491
For doubles, the 63 bit is sign, 62-52 are exponent and 51-0 are
mantissa.
The mask manipulates the bits 63-48 (ushort, 16bit)
0x8000 is
I've been talking to Iain Buclaw, gdc's leader, and was surprised to
learn he has a quite workable ARM port available. To make it
production-ready, we should have some continuous test integration, which
entails ssh access to an ARM/Debian account.
Is there anyone on this list who
1 - 100 of 492 matches
Mail list logo
