This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: ctor_copy_dtor.cc still consuming outrageous amounts of memory


> What to do, what to do...  I'll add a call to 'ulimit -v' and see what
> the memory limit needs to be set to, for starters.

With this patch, I get no nasty memory hoggers, and results of:

    pass/fail results:  98/3 shared + 98/3 static = 196/6 total

The three failing tests are the usual map/set operators, and a runtime
failure of 27_io/ios_base_members_static.  Sweet.  Do we want to increase
the memory limit that much, however?  We started at 2MB for a reason.

Phil


*** old/libstdc++-v3/mkcheck.in	Fri Jan 26 18:37:12 2001
--- new/libstdc++-v3/mkcheck.in	Mon Jan 29 04:33:12 2001
***************
*** 89,97 ****
  # the names of the specific test files to be run
  TESTS_FILE="$TEST_DIR/$(date +%Y%m%d)-mkcheckfiles.txt"
  
! # the heap size limit for testsuite binaries; start with a 2MB limit as per
! # http://gcc.gnu.org/ml/libstdc++/2000-10/msg00029.html
! MAX_MEM_USAGE=3072
  
  #
  # 2: clean, make files, append general test info
--- 89,97 ----
  # the names of the specific test files to be run
  TESTS_FILE="$TEST_DIR/$(date +%Y%m%d)-mkcheckfiles.txt"
  
! # the heap size and virtual mem limit for testsuite binaries
! # See http://gcc.gnu.org/ml/libstdc++/2000-10/msg00029.html
! MAX_MEM_USAGE=16384
  
  #
  # 2: clean, make files, append general test info
***************
*** 338,344 ****
          # printed by the executable will be lost and cannot be redirected,
          # because we need to capture the output of 'time'.  Bummer.
          TIMEFORMAT='timemark %R'
!         E_TIME_TEXT="$(exec 2>&1; ulimit -d $MAX_MEM_USAGE; \
                       time $LTEXE $EXENAME)"
          E_ABNORMAL_TERMINATION=$?
          E_TIME="$(echo $E_TIME_TEXT | awk '{print $2}')"
--- 338,345 ----
          # printed by the executable will be lost and cannot be redirected,
          # because we need to capture the output of 'time'.  Bummer.
          TIMEFORMAT='timemark %R'
!         E_TIME_TEXT="$(exec 2>&1;                                        \
!                      ulimit -d $MAX_MEM_USAGE; ulimit -v $MAX_MEM_USAGE; \
                       time $LTEXE $EXENAME)"
          E_ABNORMAL_TERMINATION=$?
          E_TIME="$(echo $E_TIME_TEXT | awk '{print $2}')"


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]