. April 2015 13:32
An: Richard Biener
Cc: Jan Hubicka; GCC Development; zl...@acm.org
Betreff: AW: g++keeps unused objects with virtual functions
That means, that there is no chance to find this in the next future GCC
releases :-(
But anyway... Thanks so far
Stefan
PS: Hope dies last
That means, that there is no chance to find this in the next future GCC
releases :-(
But anyway... Thanks so far
Stefan
PS: Hope dies last
-Ursprüngliche Nachricht-
Von: Richard Biener [mailto:richard.guent...@gmail.com]
Gesendet: Mittwoch, 08. April 2015 13:27
An: Stefan Ehrlich
Cc:
Dear Richard,
The optimization step for doing it does already exist --> it is used for stack
variables/objects, but unfortunately not for the global ones.
The same optimization should work for the global variables/objects, too. Or am
I wrong?
Stefan
-Ursprüngliche Nachricht-
Von: Rich
But without the virtual keyword the global object never read is completely
removed, so the statement "[...]but we don't have any pass removing stores to
globals never read[...]" is only true with virtual functions.
When I create the object on the stack, the optimization removes the object even
w
Dear Richard, Zan,
There are no target specifics present. The program will be flashed to the µC
via a programmer and that's it.
Therefore I want to have the output hex file as small as possible.
When I play around with my demo program and the keyword virtual, I can clearly
see that the keywork
