This result in an overall drop of 17% in performance. I think it
may be due to some stuff related to HWSURFACE, the fact it use
double buffer or that maybe SDL_FillRect was faster for cleaning up
memory. If someone is really interested by this performance drop,
better fix them with buffer engine.
SVN revision: 68351
Subject: [Patch] expedite: fix segfault at exit
shutdown the engine before evas because Xext, Xrender and GL (loaded by evas)
seem to register a hook which is called in XCloseDisplay (in engine_shutdown()).
this segfault because evas_shutdown() should unload those libs, and so,
invalidate the hook pointer.
this bug was already noted by caro in @43373:
> strangely, the xrender xlib and gl xlib engines are segfaulting when
XCloseDisplay is called (in the shutdown function). > It does not with soft
xlib. I absolutely don't know why.
with this proper fix, remove also Xext, Xrender from dependencies,
which are not used directly by expedite.
triggered by compiling with --as-needed, because it removed unused libs:
tested with xlib, gl and sdl engine
SVN revision: 65336
A button press would send '1' as the button (the pressed state) and the
release would send '0', so evas would think button 1 was never released
so it would never register any button releases.
SVN revision: 63259
Apply badzero.cocci, badnull.coci and badnull2.cocci
This should convert all cases where there's a comparison to NULL to simpler
forms. This patch applies the following transformations:
code before patch ||code after patch
return a == NULL; return !a;
return a != NULL; return !!a;
func(a == NULL); func(!a);
func(a != NULL); func(!!a);
b = a == NULL; b = !a;
b = a != NULL; b = !!a;
b = a == NULL ? c : d; b = !a ? c : d;
b = a != NULL ? c : d; b = a ? c : d;
a == NULL !a
a != NULL a
SVN revision: 51487
1. date + time you ran (or finished) the test
2. version of evas used
3. profile requested
4. actual window resolution you got
5. loop count used
6. engine used
7. fullscreen flag requested
now the results at least can be tracked over time knowing what you ran
the results on 3 months ago etc. :)
SVN revision: 50876