I'm having problems compiling GDC on Mac OS X 10.9.
I have setup the build with these instructions:
http://gdcproject.org/wiki/Installation/General
Installed xcode command line tools. I have not installed full
Xcode.
Installed GCC 4.8 from macports and set it as default gcc (gcc -v
says gc
On 2013-12-18 18:36, Iain Buclaw wrote:
I'm not so sure about 'module discovery' either. At least, in
emulated TLS, it has a completely different concept - each thread has
a dynamically allocated range (effectively, a void**[] on the heap
that gets destroyed upon thread termination) which is sh
On 18 December 2013 15:39, Johannes Pfau wrote:
> Am Tue, 17 Dec 2013 21:12:41 +0100
> schrieb "David Nadlinger" :
>
>> On Tuesday, 17 December 2013 at 20:07:41 UTC, Iain Buclaw wrote:
>> > The hidden subtext that you didn't understand being, I'm
>> > holding back on Martin's patches for now.
>>
>
On 18 December 2013 15:17, Johannes Pfau wrote:
> Am Wed, 18 Dec 2013 14:29:57 +
> schrieb Iain Buclaw :
>
>>
>> Hi Mike,
>>
>> This has been fixed to not call any library routines, but has not been
>> backported to the 4.8 branch yet.
>>
>> This is something that will be done before New Years
On 18 December 2013 15:17, Johannes Pfau wrote:
> Am Wed, 18 Dec 2013 14:29:57 +
> schrieb Iain Buclaw :
>
>>
>> Hi Mike,
>>
>> This has been fixed to not call any library routines, but has not been
>> backported to the 4.8 branch yet.
>>
>> This is something that will be done before New Years
Am Tue, 17 Dec 2013 21:12:41 +0100
schrieb "David Nadlinger" :
> On Tuesday, 17 December 2013 at 20:07:41 UTC, Iain Buclaw wrote:
> > The hidden subtext that you didn't understand being, I'm
> > holding back on Martin's patches for now.
>
> That subtext isn't exactly hidden, given the first sent
Am Wed, 18 Dec 2013 14:29:57 +
schrieb Iain Buclaw :
>
> Hi Mike,
>
> This has been fixed to not call any library routines, but has not been
> backported to the 4.8 branch yet.
>
> This is something that will be done before New Years (if my list of
> things to do does not grow even more...)
On Wednesday, 18 December 2013 at 14:31:31 UTC, Iain Buclaw wrote:
On 18 December 2013 14:29, Daniel Kozak
wrote:
Is this a bug, by design, a temporary convenience? Please
advise and
offer your suggestions?
IMHO it is not a bug. Even static arrays are dynamically
allocated and then
con
IMHO it is not a bug. Even static arrays are dynamically
allocated and then convert to static.
I mean everytime when you write [something, something else, ...]
even if all members are known at compile time, it will create
dynamic array.
On 18 December 2013 14:29, Daniel Kozak wrote:
>
>> Is this a bug, by design, a temporary convenience? Please advise and
>> offer your suggestions?
>
>
> IMHO it is not a bug. Even static arrays are dynamically allocated and then
> convert to static.
>
Not anymore, they are not. It makes no sen
Is this a bug, by design, a temporary convenience? Please
advise and offer your suggestions?
IMHO it is not a bug. Even static arrays are dynamically
allocated and then convert to static.
You can write this:
uint[3] message;
message[0] = 2;
message[1] = cast(uint)"hello\r\n".ptr;
message[
On 18 December 2013 14:14, Mike wrote:
> I finally got a GDC cross-compiler built for the ARM Cortex-M, and it seems
> to generated executable code (code that can be executed). I'm working on
> getting a *very* minimal D runtime so I can run a simple semihosted hello
> world program as I did with
I finally got a GDC cross-compiler built for the ARM Cortex-M,
and it seems to generated executable code (code that can be
executed). I'm working on getting a *very* minimal D runtime so
I can run a simple semihosted hello world program as I did with
LDC here
(http://wiki.dlang.org/Extremely_
13 matches
Mail list logo
