Build by default with optimization level -O2 for GCC

before -O0 was used by default, that caused pretty bad performance.

Amd64, i6700k, 4200MHz, GNU/Linux (non-RT kernel), gcc 7.2.0

-------------------------------------
Optimization | EN/ENO |no EN/ENO |
-------------------------------------
default | 11 | 9.5 |
-O3 | 3.9 | 5.2 |
-O2 | 4 | 4.8 |
-Os | 4.1 | 3.5 |
-Ofast | 3.9 | 5.2 |
-------------------------------------

ARM, BBB Cortex-A8, 600Mhz, GNU/Linux, gcc 4.6.3

-------------------------------------
Optimization | EN/ENO |no EN/ENO |
-------------------------------------
default | 273 | 226 |
-O3 | 141.8 | 106.2 |
-O2 | 142 | 107 |
-Os | 152.5 | 112.2 |
-Ofast | 141.7 | 106.2 |
-------------------------------------

For embedded systems with size constaints (like Cortex-Mx, AVR and so
on) I usually use -Os. It gets pretty good results. For
GNU/Linux-based systems -O2 is usually a good choice, as you see the
test results.

     1

#!/bin/sh

     2

     3

LC_ALL=ru_RU.utf-8

     4

     5

export DISPLAY=:42

     6

Xvfb $DISPLAY -screen 0 1280x1024x24 &

     7

sleep 1

     8

     9

ret=0

    10

DELAY=400

    11

KILL_DELAY=$(($DELAY + 30))

    12

timeout -k $KILL_DELAY $DELAY pytest --timeout=10 ./tests/tools

    13

ret=$?

    14

    15

pkill -9 Xvfb

    16

    17

exit $ret