This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug tree-optimization/19639] Funny (horrible) code for empty destructor
- From: "rguenth at tat dot physik dot uni-tuebingen dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 28 Jan 2005 14:21:16 -0000
- Subject: [Bug tree-optimization/19639] Funny (horrible) code for empty destructor
- References: <20050126134950.19639.rguenth@tat.physik.uni-tuebingen.de>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From rguenth at tat dot physik dot uni-tuebingen dot de 2005-01-28 14:21 -------
Folding &x.foo[2] == &x.foo to false does not help the testcase, as fold
never sees this comparison. Instead the initial code the C++ frontend
creates for ctor and dtor of arrays contains temporaries for these already.
It seems the C++ frontend tries to be clever here, creating pointer IVs for
the loop and doing too much manual optimizing.
What other pass than fold() is supposed to handle this sort of simplification?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19639