stops compiling
Deewiant
deewiant.doesnotlike.spam at gmail.com
Tue Mar 21 08:00:25 PST 2006
Thomas Kuehne wrote:
> Deewiant schrieb am 2006-03-21:
>>> Thomas Kuehne wrote:
>>>> debugger schrieb am 2006-03-19:
>
> [snip]
>
>>>> I can't reproduce this. Are you sure the code above is complete
>>>> (I see no "init4")?
>>> I think he typoed and was talking about init3, as that's the behaviour I get. I
>>> used code like this:
>>>
>>> void init1(){}
>>> void init2(){
>>> // around 16 000 calls to init1()
>>> }
>>> void init3(){ printf("hello"); }
>>> void main() { init3(); }
>>>
>>> And nothing was printed when I ran the program - in fact, -v claimed that even
>>> main() had no code generated.
>>>
>>> Approximately halving the number of calls to init1() (I wasn't counting how
>>> many, just going by his approximate 16 and 8 thousand) made it work fine.
>
> Seems to be a Windows specific bug.
>
> Does
> http://dstress.kuehne.cn/run/m/many_functions_02.d
> show the same behaviour?
>
> Thomas
>
>
Yes, it does.
D:\Main>dmd asdf.d -v
parse asdf
semantic many_functions_02
semantic2 many_functions_02
semantic3 many_functions_02
code many_functions_02
generating code for function 'init1'
generating code for function 'init2'
And no .exe is generated.
In my previous post, I already had an old asdf.exe which is why "nothing was
printed when I ran the program", instead of no program appearing there at all,
like in this case.
More information about the Digitalmars-d-bugs
mailing list