On Mar 8, 2014 9:40 AM, "Johannes Pfau" wrote:
>
> Am Sat, 08 Mar 2014 09:12:48 +
> schrieb "Mike" :
>
> > On Saturday, 8 March 2014 at 08:09:29 UTC, Timo Sintonen wrote:
> > >
> > > Why do you need synchronized? Are you building some kind of
> > > multithreading library?
> >
> > I don't need
Am Sat, 8 Mar 2014 11:45:18 +
schrieb Iain Buclaw :
>
> The next step is to fix the codegen so that it does not rely on the
> compiler knowing the critsecsize.
That's better, of course!
On 8 March 2014 09:37, Johannes Pfau wrote:
> Am Sat, 08 Mar 2014 09:12:48 +
> schrieb "Mike" :
>
>> On Saturday, 8 March 2014 at 08:09:29 UTC, Timo Sintonen wrote:
>> >
>> > Why do you need synchronized? Are you building some kind of
>> > multithreading library?
>>
>> I don't need it yet. I'
On Saturday, 8 March 2014 at 10:33:30 UTC, Timo Sintonen wrote:
In gcc build we know the host we are building and the target we
are building for.
Yeah! You are right. GDC/GCC is somewhat unique in this regard,
isn't it? critsecsize could just return a constant that's
determined at GDC's co
On Saturday, 8 March 2014 at 09:12:49 UTC, Mike wrote:
On Saturday, 8 March 2014 at 08:09:29 UTC, Timo Sintonen wrote:
Why do you need synchronized? Are you building some kind of
multithreading library?
I don't need it yet. I'm just exploring features of D and
trying to learn how to implem
Am Sat, 08 Mar 2014 09:12:48 +
schrieb "Mike" :
> On Saturday, 8 March 2014 at 08:09:29 UTC, Timo Sintonen wrote:
> >
> > Why do you need synchronized? Are you building some kind of
> > multithreading library?
>
> I don't need it yet. I'm just exploring features of D and trying
> to learn
On Saturday, 8 March 2014 at 08:09:29 UTC, Timo Sintonen wrote:
Why do you need synchronized? Are you building some kind of
multithreading library?
I don't need it yet. I'm just exploring features of D and trying
to learn how to implement them. The real problem isn't that I
can't use sync
On Saturday, 8 March 2014 at 07:52:10 UTC, Mike wrote:
I'm getting an ICE in d-target.cc/critsecsize when I create a
synchronized block. Looking at the source code, it's pretty
obvious why - my target (ARM Cortex-M bare metal) isn't any of
the ones listed:
if (global.params.isWindows)
...
I'm getting an ICE in d-target.cc/critsecsize when I create a
synchronized block. Looking at the source code, it's pretty
obvious why - my target (ARM Cortex-M bare metal) isn't any of
the ones listed:
if (global.params.isWindows)
...
else if (global.params.isLinux)
...
else if (global.pa
