Quite nice!
Joakim writes:
>>> Sound doesn't work in the official Ustream Android app either for
>>> the Dconf stream, as I noted. My guess would be that the HTML5
>>> player and the Android app try to use whatever audio codecs are
>>> built into Android, instead of the app using its own codecs, and
>>> the
Joakim writes:
> On Wednesday, 4 May 2016 at 09:13:12 UTC, Dženis Kiderič wrote:
>> On Wednesday, 4 May 2016 at 09:04:38 UTC, Dicebot wrote:
>>> On Wednesday, 4 May 2016 at 08:33:47 UTC, Joakim wrote:
There appears to be a problem with the sound on Ustream with
Android, at least for me:
Kai Nacke writes:
> Hi everyone,
>
> LDC 1.0.0-beta1, the LLVM-based D compiler, is available for download!
> This BETA release is based on the 2.070.2 frontend and standard
> library and supports LLVM 3.5-3.8.
>
> The 1.0 release will be a major milestone. Please help testing to make
> it the be
Walter Bright writes:
>
> https://www.reddit.com/r/programming/comments/4e07lo/last_night_in_a_fit_of_boredom_far_away_from_my/d1x5rl7
I am tempted to try it on my TOPS-10 (PDP-10) account at LCM. I believe
TECO is installed.
--
Dan
Adrian Matoga writes:
> On Thursday, 14 January 2016 at 20:33:30 UTC, Kai Nacke wrote:
>> LDC 0.17.0-beta1, the LLVM-based D compiler, is available for
>> download!
>> This release is based on the 2.068.2 frontend and standard library
>> and supports LLVM 3.5-3.7.
>
> Excellent! Works great so fa
Manu via Digitalmars-d-announce writes:
>
> Love your work guys! Thanks for keeping at it.
>
> One question though, what's the plan for moving to DMD latest? Both
> LDC and GDC seem to be quite behind at the moment.
> My current project is depending on bug-fixes patched in by Walter in
> the last
Laeeth Isharc writes:
> I can confirm that D also runs on Android Wear (Huawei watch) and
> passes all unit tests. Forgive the slight hijack, but I mention this
> here as people might see this thread and not the obscure one where I
> reported this previously.
I think it is a good hijack!
> Som
Joakim writes:
> On Thursday, 31 December 2015 at 00:11:34 UTC, Dan Olson wrote:
>> On Wednesday, 30 December 2015 at 23:11:06 UTC, Joakim wrote:
>>> That sounds like this issue I ran into with ARM EH:
>>>
>>> https://github.com/ldc-developers/ldc/issues/489#
Joakim writes:
> On Monday, 4 January 2016 at 09:26:39 UTC, Dan Olson wrote:
>> Joakim writes:
>>
>>> On Thursday, 31 December 2015 at 00:11:34 UTC, Dan Olson wrote:
>>>> [...]
>>>
>>> Sounds good, submit a PR and let's get it in.
>&
Joakim writes:
> On Monday, 4 January 2016 at 09:26:39 UTC, Dan Olson wrote:
>> Joakim writes:
>
>> The bug is a bad stack pointer which blows up when the last unittest
>> returns. This unittest has all the right conditions to generate
>> stack adjustments aro
Joakim writes:
> On Thursday, 31 December 2015 at 00:11:34 UTC, Dan Olson wrote:
>> On Wednesday, 30 December 2015 at 23:11:06 UTC, Joakim wrote:
>>> That sounds like this issue I ran into with ARM EH:
>>>
>>> https://github.com/ldc-developers/ldc/issues/489#
On Wednesday, 30 December 2015 at 23:11:06 UTC, Joakim wrote:
That sounds like this issue I ran into with ARM EH:
https://github.com/ldc-developers/ldc/issues/489#issuecomment-143560075
I was able to work around it by disabling the mentioned llvm
optimization pass:
https://gist.github.com/jo
Dan Olson writes:
> A little progress report. More to come later when I get something pushed
> to github.
>
> I bought a returned Apple Watch yesterday at discount for $223.99 US and
> tried to see how much of D would work on it using my iOS fork of LDC.
> There were a few b
Jacob Carlborg writes:
> On 2015-12-30 08:02, Dan Olson wrote:
>
>> I know some of it from hacking dyld for iOS, but not all. How does this
>> fit in with "Plan B.2"?
>
> If you need to figure out how TLS works, I can give you some help,
> that's all
Jacob Carlborg writes:
> On 2015-12-28 20:02, Dan Olson wrote:
>
>> That is Plan B.2
>
> I'm working on implementing native TLS for OS X in DMD. I think I've
> figured out how everything works. Unless you already know how it
> works, I could tell you what I ha
Jacob Carlborg writes:
>
> Would it be possible to bypass LLVM and do the thread local specific
> parts in LDC?
That is Plan B.2
Joakim writes:
>
> Thanks for the detailed answer; I'm sure this will now become the
> definitive answer online. I've gone googling for technical info only
> to sometimes be directed back to a post in these D forums. :)
Me too! Its very funny when that happens.
> Time to get emulated TLS for M
Joakim writes:
>
> I don't understand how the bitcode requirement works on your own
> device: I thought that was for an Apple-submitted app that they then
> compiled to binary themselves? Do you have to go through the same
> process even for test apps, ie no sideloading? Or does the device
> its
A little progress report. More to come later when I get something pushed
to github.
I bought a returned Apple Watch yesterday at discount for $223.99 US and
tried to see how much of D would work on it using my iOS fork of LDC.
There were a few bumps, like dealing with embedded bitcode (a watchOS
r
Kai Nacke writes:
> Hi everyone,
>
> LDC 0.17.0-alpha1, the LLVM-based D compiler, is available for
> download!
> This release is based on the 2.068.2 frontend and standard library and
> supports LLVM 3.5-3.7.
>
> Don't miss to check if your preferred system is supported by this
> release. We als
Joakim writes:
> On Saturday, 7 November 2015 at 20:34:06 UTC, Dan Olson wrote:
>> Joakim writes:
>>> Hmm, that's strange, this commit didn't fix the 64-bit issues for
>>> you? I believe it fixed them for me on Android/ARM:
>>>
>&
Joakim writes:
> On Saturday, 7 November 2015 at 19:20:02 UTC, Dan Olson wrote:
>> Dan Olson writes:
>>
>>> Joakim writes:
>>>> btw, std.internal.math.gammafunction hasn't given me a problem
>>>> since 2.067.1, the Win64 guys fixed it. 2.06
Dan Olson writes:
> Joakim writes:
>> btw, std.internal.math.gammafunction hasn't given me a problem since
>> 2.067.1, the Win64 guys fixed it. 2.068 added a function that needs a
>> CTFE-able 64-bit log2, but other than that, it just works now. You
>> may wa
Go mobile!
Joakim writes:
> btw, std.internal.math.gammafunction hasn't given me a problem since
> 2.067.1, the Win64 guys fixed it. 2.068 added a function that needs a
> CTFE-able 64-bit log2, but other than that, it just works now. You
> may want to revert your patch for that module and try it.
Thanks f
Joakim writes:
> Great, your last announcement was linked in reddit comments about the
> 2.069 release, when asked about iOS support.
>
> On Thursday, 5 November 2015 at 08:05:39 UTC, Dan Olson wrote:
>> Just noticed that tvOS and watchOS are now present in LLVM, so I
>>
Just a few more notes:
Dan Olson writes:
> Feedback appreciated, especially since iOS support may get into official
> LDC sometime soon. This is a good time to voice an opinion on the
> approach.
Just noticed that tvOS and watchOS are now present in LLVM, so I think
support for these
This is another set of binaries and universal libs for the experimental
LDC iOS cross-compiler. It is now based on LDC 0.16.1 (2.067.1) and
LLVM 3.6.2.
https://github.com/smolt/ldc-iphone-dev/releases/tag/ios-0.16.1-151104
Feedback appreciated, especially since iOS support may get into official
Jacob Carlborg writes:
> On 2015-10-24 12:01, Suliman wrote:
>
>> Would it be hard to add Windows/Linux host available? Would it be hard
>> to develop iOS apps on Windows in comparison of using MacOSX?
>
> It depends on what you mean. Microsoft already supports developing iOS
> apps on Windows, b
extrawurst writes:
> On Saturday, 24 October 2015 at 07:07:18 UTC, Dan Olson wrote:
>> This is another set of binaries and universal libs for the
>> experimental LDC iOS cross-compiler. It is now based on LDC 0.15.2
>> (2.066.1) and LLVM 3.6.1.
>>
>> [...]
>
This is another set of binaries and universal libs for the experimental
LDC iOS cross-compiler. It is now based on LDC 0.15.2 (2.066.1) and
LLVM 3.6.1.
https://github.com/smolt/ldc-iphone-dev/releases/tag/ios-0.15.2-151023
What's new?
- arm64 for iOS 64-bit devices
- C ABI compatibility improvem
"Colden Cullen" writes:
> On Sunday, 2 August 2015 at 22:53:00 UTC, Walter Bright wrote:
>> Seeing the threads on London, Silicon Valley and Berlin meetups, is
>> there any interest for a Seattle one?
>
> Yes please! Myself and a good portion of the Dash[1] team are in
> Seattle now, and we'd lov
Very good news!
"Jack Stouffer" writes:
>
> Does this have any way to call the iOS Obj-C libraries for UI
> rendering and the like? Or is that a separate project?
It is a separate project and is gradually getting pulled into DMD:
http://forum.dlang.org/post/mnm1sf$kp8$1...@digitalmars.com
For now, you can writ
Manu via Digitalmars-d-announce writes:
>
> Possible to make cross compilers for other hosts?
> Who uses a mac? ;)
Hi Manu - I wish I knew the answer. I assume you are thinking Windows.
I just looked at some stackoverflow answers, specifically at Xamarin.iOS
for Windows, and all seem to require
I've made a set of binaries and universal libs for the LDC iOS
cross-compiler. It is based on LDC 0.15.1 (2.066) and LLVM 3.5.1.
https://github.com/smolt/ldc-iphone-dev/releases/tag/ios-0.15.1-150708
Only 32-bit devices currently; arm64 work starts next month when I
acquire an iPhone 6.
The dow
Steven Schveighoffer writes:
> On 6/1/15 11:40 AM, Dan Olson wrote:
>> "Dicebot" writes:
>>
>>> - Moving fibers between threads (though there is some hope that Liran
>>> managed to convince Walter it is a bad idea)
>>
>> I am interesting
"Dicebot" writes:
> - Moving fibers between threads (though there is some hope that Liran
> managed to convince Walter it is a bad idea)
I am interesting in this one. What was the decision, that Fibers should
or should not be allowed to migrate between threads? Is the discussion
in one of the
body thought of porting relavant
parts of say newlib to D?
--
Dan Olson
"Abdulhaq" writes:
> On Tuesday, 14 April 2015 at 16:17:37 UTC, Justin Whear wrote:
>> EMSI is hiring for an Engineer II to work on D codebases: https://
>> emsi.bamboohr.com/jobs/view.php?id=30
>
> When it said Moscow I was thinking mmmh lots of traffic, a bit
> difficult to live in then I s
"Kingsley" writes:
> In preparation for the London D meetup I have got the DTanks robot
> battle framework into the first alpha release state - good enough to
> use at the meetup anyway.
>
> https://github.com/masterthought/dtanks
>
> --K
DTanks looks cool! I am going to have to try it. Brings
Dan Olson writes:
> "Kai Nacke" writes:
>
>> On Sunday, 1 March 2015 at 03:26:16 UTC, Dan Olson wrote:
>>> Dan Olson writes:
>>>
>>> I got LLVM 3.6 to work but I couldn't compile with LDC 0.15.1 (looks
>>> like more 3.6 fixes cam
"Kai Nacke" writes:
> On Sunday, 1 March 2015 at 03:26:16 UTC, Dan Olson wrote:
>> Dan Olson writes:
>>
>> I got LLVM 3.6 to work but I couldn't compile with LDC 0.15.1 (looks
>> like more 3.6 fixes came in after it) and ldc master HEAD
>> compil
Dan Olson writes:
> "Kai Nacke" writes:
>
>> Also note that LDC is mentioned in the release notes as one of the
>> projects who are already supporting LLVM 3.6. Just recompile LDC using
>> master branch from GitHub or from the 0.15.1 source.
>>
&g
"Kai Nacke" writes:
> Also note that LDC is mentioned in the release notes as one of the
> projects who are already supporting LLVM 3.6. Just recompile LDC using
> master branch from GitHub or from the 0.15.1 source.
>
> This is the 6th time that LDC and D are mentioned in the LLVM release
> note
On Thursday, 26 February 2015 at 19:26:07 UTC, Jacob Carlborg
wrote:
I could successfully compile the compiler and compile Hello
World without any problems. I did not try running it on an a
device.
Thanks Jacob!
I think this all is in good enough shape that someone else should give
it a try.
https://github.com/smolt/ldc-iphone-dev
This is an LDC development sandbox for iPhone iOS.
It glues together various pieces needed to build an LDC cross compiler
targeting iPhoneOS. It also includes a few samples t
Johannes Pfau writes:
> iOS:
> I don't know about gdc/iOS but there seems to be some work on this
> for LDC:
> http://forum.dlang.org/thread/m2txc2kqxv@comcast.net
I tried adding iOS support to GDC a year ago, but the arm--darwin target
is missing in gcc since 4.2. It was turning into a lot
"Szymon Gatner" writes:
> Wow, this is fantastic! This and recent progress on iOS/ARM/LDC
> porting make me so happy :)
Yeah, it will be cool to combine this with the LDC iOS work. I haven't
posted progress lately. I got Fibers working on an iPhone 4. I found
that GDC's thread.d already had A
"w0rp" writes:
> This is really awesome work. If you combined ARM support with
> Objective C support, it would mean you could write iOS programs
> in D without much frustration, and that would be a huge step
> forward. Objective C has a good runtime, but lacks templates and
> CTFE. Using CTFE
Now this is very good. I so badly have wanted the simple data rep that
lisp has builtin and this is almost it. XML, in my opinion, is ugly and
overly verbose. JASON was better. SDL looks to be just about right.
--
dano
52 matches
Mail list logo
