I don't really like this. Maybe only do this on the build server, or at
least don't do it to kernel code. "Measurable" difference in performance
doesn't really mean much on an OS that does not have any performance
infrastructure, but trust me, there's a difference between O1 and O2.
Best regards,
Alex Ionescu
On Wed, Jul 31, 2013 at 6:04 AM, <akhaldi(a)svn.reactos.org> wrote:
> Author: akhaldi
> Date: Wed Jul 31 13:04:38 2013
> New Revision: 59598
>
> URL: http://svn.reactos.org/svn/reactos?rev=59598&view=rev
> Log:
> [CMAKE/GCC]
> * Compile debug builds using -O1 instead of -Os. This results in faster
> compilation time with no measurable difference in runtime performance
> according to tests.
> CORE-7374 #resolve #comment Committed in r59598.
>
> Modified:
> trunk/reactos/cmake/config.cmake
>
> Modified: trunk/reactos/cmake/config.cmake
> URL:
> http://svn.reactos.org/svn/reactos/trunk/reactos/cmake/config.cmake?rev=595…
>
> ==============================================================================
> --- trunk/reactos/cmake/config.cmake [iso-8859-1] (original)
> +++ trunk/reactos/cmake/config.cmake [iso-8859-1] Wed Jul 31 13:04:38
> 2013
> @@ -10,7 +10,7 @@
> set(TUNE "i686" CACHE STRING
> "Which CPU ReactOS should be optimized for.")
>
> -set(OPTIMIZE "1" CACHE STRING
> +set(OPTIMIZE "4" CACHE STRING
> "What level of optimization to use.
> 0 = off
> 1 = Default option, optimize for size (-Os) with some additional options
>
>
>
Hello,
Let me invite you to the monthly status meeting taking place last
Thursday of this month, 25th of Julu, 19:00 UTC. Put that into your
calendars so you don't forget.
I will handle the technical side of the meeting and you will get your
login credentials shortly before the meeting. If someone still is not
getting passwords sent before a meeting - please email Colin or Pierre
before the meeting started to get one.
The agenda will be posted shortly before the meeting, suggestions are
welcome (preferably send them to me before the meeting starts).
Regards,
Aleksey Bragin
Hi,
For all TSVN users: the new version 1.8.0 is broken. Merging doesn't
work and aborts once you get a conflict. I had to install a nightly to
make that work.
Also: it uses a new working copy format, which is incompatible with
older svn versions, like the one we use in RosBE. Which you would also
need to update.
Therefore I suggest to not update it yet, unless you really know what
you are doing. I don't want to hear complaints later ;-)
Timo