[ros-kernel] GCC Optimizaitons on Speed-Critical Code

[Alex Ionescu]

Hi,

>> I'm myself building my Win32k optimized and the speed improvement is 
>> noticeable.

Excellent, exactly as I thought. Win32K is one of the areas I think should
really be built with optimizations.

>> The problem is that our HAL doesn't work when compiled with optimization

Any clues as to why? This is usually a sign of hard-coded pointers or other
bad practices...they'd have to be fixed someday anyhow. I don't know however
if HAL can really benefit from speed optimizations... then again, I don't
know much about HAL.

>> if the whole ReactOS is build with "-O2 -Wno-strict-aliasing" it feels a
>> lot slower because of some component (maybe Freetype?).

Personally, I am against building the whole OS with -O2 right now because it
slows down the build process too much, and not all parts need it.

>> Also it should be an option, because it's easier to debug un-optimized
>> binaries.

Agreed. However I think that option should be by default for User-Builds (as
in Releases). That way the general users can make use of them. Or perhaps
provide, a-la Microsoft an optimized/unoptimized build image.

Best regards,
Alex Ionescu

-----Original Message-----
From: ros-kernel-bounces at reactos.com [mailto:ros-kernel-bounces at reactos.com]
On Behalf Of Filip Navara
Sent: July 17, 2004 6:52 PM
To: ReactOS Kernel List
Subject: Re: [ros-kernel] GCC Optimizaitons on Speed-Critical Code

Alex Ionescu wrote:

>Hi,
>
>I've noticed that we don't seem to use the slightest GCC optimization
flags.
>I know this would slow down the build if used everywhere, but I believe
that
>some parts of the code would greatly benefit from it, such as Win32K or
>Syncronization/Locking code in ntoskrnl. There are probably other places
>too.
>What do all think? Would this be bad for any reason?
>  
>
I'm myself building my Win32k optimized and the speed improvement is 
noticable. The problem is that our HAL doesn't work when compiled with 
optimalization and if the whole ReactOS is build with "-O2 
-Wno-strict-aliasing" it feels a lot slower because of some component 
(maybe Freetype?). We would need to solve these issues first. Also it 
should be an option, because it's easier to debug unoptimized binaries.

Regards,
Filip
_______________________________________________
Ros-kernel mailing list
Ros-kernel at reactos.com
http://reactos.com/mailman/listinfo/ros-kernel