------- Comment #3 from rguenth at gcc dot gnu dot org 2010-07-01 08:20 ------- (In reply to comment #2) > 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?
We are going to ask developers to use -fno-builtin-malloc for now. I also think this is a glibc bug which should mark the hook variables volatile. So, can you file a bug in the glibc bugzilla as well? > Thanks again. > -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44736
