From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18066 invoked by alias); 25 Mar 2004 20:47:48 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 18038 invoked from network); 25 Mar 2004 20:47:47 -0000 Received: from unknown (HELO bluesmobile.specifixinc.com) (64.62.200.227) by sources.redhat.com with SMTP; 25 Mar 2004 20:47:47 -0000 Received: from localhost.localdomain (bluesmobile.corp.specifixinc.com [10.0.0.1]) by bluesmobile.specifixinc.com (Postfix) with ESMTP id CD965164DD; Thu, 25 Mar 2004 12:47:46 -0800 (PST) Subject: Re: m68k-linux regressions From: Jim Wilson To: Bernardo Innocenti Cc: Richard Zidlicky , GCC Mailing List , Gunther Nikl In-Reply-To: <405E0C27.1010102@develer.com> References: <405BBE7B.4000904@develer.com> <20040321201636.GA1186@linux-m68k.org> <405E0C27.1010102@develer.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Thu, 25 Mar 2004 23:25:00 -0000 Message-Id: <1080247669.1484.15.camel@leaf.tuliptree.org> Mime-Version: 1.0 X-SW-Source: 2004-03/txt/msg01518.txt.bz2 On Sun, 2004-03-21 at 13:41, Bernardo Innocenti wrote: > Where do I change Dejagnu's default timeout for the gcc.dg > testsuite? There are some differences here depending on exactly how you are running programs, e.g. by directly invoking them, by invoking gdb and running them inside gdb, by using kermit to connect to a target, by running them under a simulator, etc. For a native linux, you are probably running them directly, in which case I think the default timeout comes from dejagnu/lib/remote.exp. Search for "set timeout 300", which sets the default to 5 minutes. You shouldn't actually modify this file though, You should write your own target file, e.g. baseboards/m68k-linux.exp, and set timeout there to override the default. You could start by just copying the unix.exp file. You would then use --target_board=m68k-linux to run the tests. If "set timeout" doesn't work, try "set_board_info gcc,timeout". -- Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com