Re: [Vala] Tons of _tmpX_ variables and other performance issues



Am Mittwoch, den 22.02.2012, 15:52 +0100 schrieb marcin saepia net:
I assume that this kind of code is a result of internal logic of
valac, but isn't it possible to avoid such things like "_tmp26_ =
_tmp25_"?

I am afraid that they unnecessary affect the performance (in average
valac output there are tons of assignments like that mentioned above)
- or maybe gcc is smart enough to optimize them?

If gcc won't do that, are there any plans to optimize that in valac? 

Optimizations are currently left to gcc, which should catch cases like
the one above - when compiled with e.g. -O3

- fabian




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]