This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug tree-optimization/34864] array constants after inlining and "staticification"
- From: "tbptbp at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 14 Feb 2008 10:02:13 -0000
- Subject: [Bug tree-optimization/34864] array constants after inlining and "staticification"
- References: <bug-34864-9709@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #4 from tbptbp at gmail dot com 2008-02-14 10:02 -------
Hmm. If i correctly understand what you're saying, *cough*, ldexp should be
immune to this missed-folding-because-a-builtin-isn't-recognized-as-such; but
in the original code that lead to PR34774 there's nothing but ldexp, yet *some*
of them occur at runtime under some weird conditions.
Of course i'd prefer to use a properly typed ldexp better than hope the
compiler realize it's about mere floats and not doubles, but that would be the
icing on the cake :)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34864