------- Comment #2 from opensource3141 at gmail dot com 2010-07-01 00:32 ------- Thanks for the lightening fast response. I wouldn't have known to look there, especially since older GCC versions did not have this problem.
Is it because 4.5.0 has better optimizations such that the code surrounding this malloc is now optimized away in this situation? Finally, is this issue going to be resolved within GCC, or is the permanent fix going to be to ask developers to use -fno-builtin-malloc? Thanks again. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44736
