compiling dmd

Marco Leise Marco.Leise at gmx.de
Sat Dec 31 06:55:34 PST 2011


Am 29.12.2011, 09:16 Uhr, schrieb Don <nospam at nospam.com>:

> On 28.12.2011 13:14, Timon Gehr wrote:
>> On 12/28/2011 10:53 AM, Peter Alexander wrote:
>>> On 27/12/11 8:40 PM, Andrei Alexandrescu wrote:
>>>> On 12/27/11 2:38 PM, Walter Bright wrote:
>>>>> On 12/27/2011 12:28 PM, Andrei Alexandrescu wrote:
>>>>>> One good realization to make is how less efficient that makes you.  
>>>>>> You
>>>>>> got used
>>>>>> to that overhead so plentily, you consider it now par for the  
>>>>>> course.
>>>>>
>>>>> What takes time is running the unittests, not compiling dmd.
>>>>
>>>> Then _that_ is what you consider par for the course! :o)
>>>>
>>>> Andrei
>>>
>>> Has anyone looked into what causes the unittests to take so long? I  
>>> find
>>> it hard to believe that they need to take as long as they do.
>>
>> They have to be run for many different combinations of compiler flags  
>> iirc.
> AFAIK there has never been a failure which wasn't with one of:
> (no flags)
> -O -release -inline
> -g -O -release -inline
>
> But why do the Phobos unit tests take so long? They used to take a  
> matter of seconds, now they take forever.
>
> On D1, they still take only about 10 seconds. On D2 they are now longer  
> than the compiler tests with the minimal flag options.

2.055 hat problems with -O -release -inline -noboundscheck (three of those  
anyway, including noboundscheck)


More information about the Digitalmars-d mailing list