dmd 1.048 and 2.033 releases

[Don]

Nick Sabalausky wrote:
> "Nick Sabalausky" <a at a.a> wrote in message 
> news:hadst9$581$1 at digitalmars.com...
>> "Walter Bright" <newshound1 at digitalmars.com> wrote in message 
>> news:hadqcs$30n8$2 at digitalmars.com...
>>> BCS wrote:
>>>> Hello Walter,
>>>>
>>>>> #ponce wrote:
>>>>>
>>>>>> I think it's disabled in debug mode to keep the compilation time low.
>>>>>>
>>>>> That, and the optimizer tends to scramble the relationship between
>>>>> source and assembler, making source debugging next to impossible.
>>>>>
>>>> How hard would it be to have the code generate run on the unoptimized 
>>>> code and then do the optimizer backed test and only if no bugs jump out, 
>>>> move the results into the object file?
>>>>
>>> It seems even easier to just compile with -0.
>> It isn't. *Very* typical workflow:
>>
> [stuff]
>> None of those are particularly good options, and I don't see any other 
>> possibilities.
>>
> 
> ...Plus it's just plain unintuitive.

It's pretty standard, though. For example, there are some bugs which 
Visual C++ detects only when the optimiser is on. From memory, they are 
all flow-related. The MS docs recommend compiling a release build 
occasionally to catch them.