Re: Optimization level iteration for dg framework

[Jeffrey A Law <law at cygnus dot com>]

  In message <20000703190725.U274@wolery.cumb.org>you write:
  > This patch implements optimization-level iteration (as is done in
  > c-torture) for the dg framework.  At the moment it's only active in
  > gcc.dg/noncompile, because some of the top level tests don't like
  > being run over and over with different options.  If the patch is
  > approved, I'll split the top level tests into ones that should and
  > ones that should not be iterated.
  > 
  > There is unfortunately no way short of modifying dejagnu itself to get
  > the optimization level into the PASS: or FAIL: messages.  (I'm not a
  > dejagnu expert, and I would be delighted to be proven wrong.)
  > 
  > Some of this code is copied from c-torture.exp and should probably be
  > factored out into an overall gcc library file.
  > 
  > zw
  > 
  > 	* lib/gcc-dg.exp: Set up TORTURE_OPTIONS, torture_with_loops,
  > 	and torture_without_loops as is done by c-torture.exp.
  > 	(search_for): Copy from c-torture.exp.
  > 	(gcc-dg-runtest): New function, drives a directory of tests
  > 	iterating over the TORTURE_OPTIONS.
  > 	(scan-assembler, scan-assembler-not): Move here from
  > 	individual directory drivers.
  > 
  > 	* gcc.dg/dg.exp: scan-assembler, scan-assembler-not now
  > 	defined by lib/gcc-dg.exp.
  > 	* gcc.dg/cpp/cpp.exp: Likewise.
  > 	* gcc.dg/noncompile/noncompile.exp: Likewise.  Use
  > 	gcc-dg-runtest, so we cycle over optimization options.
This is fine.  Please install this patch.

jeff