From c42a19d5e3a8236af3b727cd708bac22a8608b9d Mon Sep 17 00:00:00 2001 From: Thomas Koenig Date: Thu, 12 May 2005 17:50:33 +0000 Subject: re PR libfortran/21324 (#undef GFC_CLEAR_MEMORY causes testsuite failures) 2005-05-12 Thomas Koenig PR libfortran/21324 * runtime/memory.c: Don't define GFC_CLEAR_MEMORY (it's a performance hog). * io/open.c (new_unit): Zero freshly allocated memory for unit structure. * io/unit.c (init_units): Zero freshly allocated memory for STDIN, STDOUT and STDERR. * io/unix.c (open_internal): Zero freshly allocated memory for unix_stream. (fd_to_stream): Likewise. From-SVN: r99619 --- libgfortran/runtime/memory.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'libgfortran/runtime') diff --git a/libgfortran/runtime/memory.c b/libgfortran/runtime/memory.c index 8b8dca8..ce2dc91 100644 --- a/libgfortran/runtime/memory.c +++ b/libgfortran/runtime/memory.c @@ -36,7 +36,7 @@ Boston, MA 02111-1307, USA. */ return memory that is guaranteed to be set to zero. This can have a severe efficiency penalty, so it should never be set if good performance is desired, but it can help when you're debugging code. */ -#define GFC_CLEAR_MEMORY +/* #define GFC_CLEAR_MEMORY */ /* If GFC_CHECK_MEMORY is defined, we do some sanity checks at runtime. This causes small overhead, but again, it also helps debugging. */ -- cgit v1.1