Subversion Repositories openrisc_2011-10-31

/reg_search File deleted

reg_search Property changes : Deleted: svn:executable ## -1 +0,0 ## -* \ No newline at end of property Index: ChangeLog =================================================================== --- ChangeLog (revision 154) +++ ChangeLog (nonexistent) @@ -1,32 +0,0 @@ -2007-10-07 Release Manager - - * GCC 4.2.2 released. - -2007-07-19 Release Manager - - * GCC 4.2.1 released. - -2007-05-13 Release Manager - - * GCC 4.2.0 released. - -2005-07-14 Ben Elliston - - * reg_test_template: Typo fix. - -2005-01-17 Kazu Hirata - - * reg_periodic, reg_search: Fix the uses of date command. - -2003-06-24 Janis Johnson - - * reg_search: Replace existing uses of DATE with MADE_DATE and - use DATE for the date command. - * reg_periodic: Ditto. - -2003-03-27 Janis Johnson - * README: New file. - * reg_search: New file. - * reg_periodic: New file. - * reg_test_template: New file. - Index: reg_test_template =================================================================== --- reg_test_template (revision 154) +++ reg_test_template (nonexistent) @@ -1,41 +0,0 @@ -#! /bin/sh - -# Template for the test script specified for REG_TEST. - -# Run the test case for a regression search. The argument is the date -# of the sources. The return value is 1 if the binary search should -# continue with later dates, 0 if it should continue with earlier -# dates. - -DATE="${1}" - -# Specify the PR number and the directory where the test should be run. -PR=xxxx -DIR=xxxx - -LOG_DATE="`echo ${DATE} | sed 's/[-: ]/_/g'`" -LOG="${PR}.${LOG_DATE}.out" - -echo "`date` running test for PR ${PR}" -cd ${DIR} - -# Compile the test case with whatever options are needed to trigger the -# error. - - ${PR}. > ${LOG} 2>&1 - -# Some tests will require additional commands to determine whether the -# test passed or failed, such as grepping compiler output for a -# particular message, or running the test and possibly comparing its -# output with the expected output. - -xxxxx - -# The return value depends on whether the last command is expected to be -# zero or nonzero for a passing test, and whether we're looking for a -# regression or for the patch that fixed the bug. - -# Return 1 to continue the search with later dates, 0 for earlier dates. - -test $? -eq 0 && exit 1 -exit 0

reg_test_template Property changes : Deleted: svn:executable ## -1 +0,0 ## -* \ No newline at end of property Index: reg_periodic =================================================================== --- reg_periodic (revision 154) +++ reg_periodic (nonexistent) @@ -1,171 +0,0 @@ -#! /bin/bash - -######################################################################## -# -# File: reg_periodic -# Author: Janis Johnson -# Date: 2002/12/28 -# -# Over a range of dates at specified intervals, invoke separate tools to -# update sources, do a build, and run one or more tests. -# -# Define these in a file whose name is the argument to this script: -# LOW_DATE: Date string recognized by the date command. -# HIGH_DATE: Date string recognized by the date command. -# INTERVAL: Time (in seconds) between dates for which to build. -# REG_UPDATE: Pathname of script to update your source tree. -# REG_BUILD: Pathname of script to build enough of the product to run -# the test. -# REG_TEST: Pathname of script to run one or more tests. -# Optional: -# VERBOSITY: Default is 0, to print only errors and final message. -# DATE_IN_MSG If set to anything but 0, include the time and date in -# messages -# REG_STOP Pathname of a file whose existence says to quit; default -# is STOP in the current directory. -# -# -# Copyright (c) 2002, 2003, 2005 Free Software Foundation, Inc. -# -# This file is free software; you can redistribute it and/or modify -# it under the terms of the GNU General Public License as published by -# the Free Software Foundation; either version 2 of the License, or -# (at your option) any later version. -# -# This program is distributed in the hope that it will be useful, -# but WITHOUT ANY WARRANTY; without even the implied warranty of -# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the -# GNU General Public License for more details. -# -# For a copy of the GNU General Public License, write the the -# Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, -# Boston, MA 02110-1301, USA. -# -######################################################################## - -######################################################################## -# Functions -######################################################################## - -# Issue a message if its verbosity level is high enough. - -msg() { - test ${1} -gt ${VERBOSITY} && return - - if [ "x${DATE_IN_MSG}" = "x" ]; then - echo "${2}" - else - echo "`${DATE}` ${2}" - fi -} - -# Issue an error message and exit with a nonzero status. - -error() { - msg 0 "error: ${1}" - exit 1 -} - -# Turn seconds since the epoch into a date we can use with source -# control tools and report to the user. - -make_date() { - MADE_DATE="`${DATE} -u +\"%Y-%m-%d %H:%M %Z\" --date \"1970-01-01 ${1} seconds\"`" \ - || error "make_date: date command failed" -} - -# Build the components to test using sources as of a particular date and -# run a test case. Pass each of the scripts the date that we're -# testing; the first one needs it, the others can ignore it if they want. - -process_date() { - TEST_DATE="${1}" - - ${REG_UPDATE} "${TEST_DATE}" - if [ $? -ne 0 ]; then - msg 0 "source update failed for ${TEST_DATE}" - return - fi - ${REG_BUILD} "${TEST_DATE}" - if [ $? -ne 0 ]; then - msg 0 "build failed for ${TEST_DATE}" - return - fi - ${REG_TEST} "${TEST_DATE}" -} - -######################################################################## -# Main program (so to speak) -######################################################################## - -# If DATE isn't defined, use the default date command; the configuration -# file can override this. - -if [ "x${DATE}" = "x" ]; then - DATE=date -fi - -# Process the configuration file. - -if [ $# -ne 1 ]; then - echo Usage: $0 config_file - exit 1 -fi - -CONFIG=${1} -if [ ! -f ${CONFIG} ]; then - error "configuration file ${CONFIG} does not exist" -fi - -# OK, the config file exists. Source it, make sure required parameters -# are defined and their files exist, and give default values to optional -# parameters. - -. ${CONFIG} - -test "x${REG_UPDATE}" = "x" && error "REG_UPDATE is not defined" -test "x${REG_BUILD}" = "x" && error "REG_BUILD is not defined" -test "x${REG_TEST}" = "x" && error "REG_TEST is not defined" -test "x${INTERVAL}" = "x" && error "INTERVAL is not defined" -test -x ${REG_TEST} || error "REG_TEST is not an executable file" -test "x${VERBOSITY}" = "x" && VERBOSITY=0 -test "x${REG_STOP}" = "x" && REG_STOP="STOP" - -msg 2 "LOW_DATE = ${LOW_DATE}" -msg 2 "HIGH_DATE = ${HIGH_DATE}" -msg 2 "INTERVAL = ${INTERVAL}" -msg 2 "REG_UPDATE = ${REG_UPDATE}" -msg 2 "REG_BUILD = ${REG_BUILD}" -msg 2 "REG_TEST = ${REG_TEST}" -msg 2 "VERBOSITY = ${VERBOSITY}" - -# Change the dates into seconds since the epoch. This uses an extension -# in GNU date. - -LOW_DATE=`${DATE} +%s --date "${LOW_DATE}"` || \ - error "date command failed for \"${LOW_DATE}\"" -HIGH_DATE=`${DATE} +%s --date "${HIGH_DATE}"` || \ - error "date command failed for \"${LOW_DATE}\"" - -# Process each date in the range. - -while [ ${LOW_DATE} -le ${HIGH_DATE} ]; do - - # If a file called STOP appears, stop; this allows a clean way to - # interrupt a search. - - if [ -f ${REG_STOP} ]; then - msg 0 "STOP file detected" - rm -f ${REG_STOP} - exit 1 - fi - - # Get a version of the date that is usable by tools and readable - # by people, then process it. - - make_date ${LOW_DATE} - process_date "${MADE_DATE}" - let LOW_DATE=LOW_DATE+INTERVAL -done - -msg 1 "done"

reg_periodic Property changes : Deleted: svn:executable ## -1 +0,0 ## -* \ No newline at end of property Index: README =================================================================== --- README (revision 154) +++ README (nonexistent) @@ -1,16 +0,0 @@ -This directory contains scripts that are used for identifying the -patch that introduced a regression. General information about such -searches is covered in http://gcc.gnu.org/bugs/reghunt.html. - - reg_search searches for a small time interval within a range of - dates in which results for a test changed, using a binary search. - The functionality for getting sources, building the component to - test, and running the test are in other scripts that are run from - here. - - reg_periodic invokes separate tools (the same scripts invoked by - reg_search) over a range of dates at specified intervals. - - reg_test_template shows the format for the script that runs a test - and determines whether to continue the search with a later or - earlier date.