From: DJ Delorie <dj@redhat.com>
To: gcc-patches@gcc.gnu.org
Subject: [patch] testsuite: support board_info timeouts
Date: Tue, 10 Aug 2010 04:08:00 -0000 [thread overview]
Message-ID: <201008100348.o7A3mVG7009468@greed.delorie.com> (raw)
Is there any reason why we don't support board-level timeouts? It's
really hard to specify timeouts for sid-based embedded targets with
lots of multilibs (or just one, sometimes).
It's certainly better than "really REALLY ugly" which is the only
other option at that point.
* lib/timeout.exp (timeout): Add board_info support.
2010-08-09 Thomas Koenig <tkoenig@gcc.gnu.org>
Index: lib/timeout.exp
===================================================================
--- lib/timeout.exp (revision 163048)
+++ lib/timeout.exp (working copy)
@@ -43,12 +43,14 @@ proc timeout_value { args } {
if [info exists individual_timeout] {
set val $individual_timeout
} elseif [info exists tool_timeout] {
set val $tool_timeout
} elseif [target_info exists gcc,timeout] {
set val [target_info gcc,timeout]
+ } elseif [board_info target exists gcc,timeout] {
+ set val [board_info target gcc,timeout]
} else {
# This is really, REALLY ugly, but this is the default from
# remote.exp deep within DejaGnu.
set val 300
}
next reply other threads:[~2010-08-10 3:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 4:08 DJ Delorie [this message]
2010-08-10 5:09 ` Mike Stump
2011-06-02 16:49 ` DJ Delorie
2011-06-02 17:28 ` Mike Stump
2011-06-02 18:16 ` DJ Delorie
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=201008100348.o7A3mVG7009468@greed.delorie.com \
--to=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.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).