From: Jim Wilson <wilson@specifixinc.com>
To: Bernardo Innocenti <bernie@develer.com>
Cc: Richard Zidlicky <rz@linux-m68k.org>,
GCC Mailing List <gcc@gcc.gnu.org>, Gunther Nikl <gni@gecko.de>
Subject: Re: m68k-linux regressions
Date: Thu, 25 Mar 2004 23:25:00 -0000 [thread overview]
Message-ID: <1080247669.1484.15.camel@leaf.tuliptree.org> (raw)
In-Reply-To: <405E0C27.1010102@develer.com>
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
next prev parent reply other threads:[~2004-03-25 20:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-20 6:48 Bernardo Innocenti
2004-03-22 1:27 ` Richard Zidlicky
2004-03-22 4:30 ` Bernardo Innocenti
2004-03-22 7:48 ` Bernardo Innocenti
2004-03-25 23:25 ` Jim Wilson [this message]
2004-03-22 5:16 ` Matthias Klose
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1080247669.1484.15.camel@leaf.tuliptree.org \
--to=wilson@specifixinc.com \
--cc=bernie@develer.com \
--cc=gcc@gcc.gnu.org \
--cc=gni@gecko.de \
--cc=rz@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).