From patchwork Tue Aug 10 03:48:31 2010 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: testsuite: support board_info timeouts X-Patchwork-Submitter: DJ Delorie X-Patchwork-Id: 61332 Message-Id: <201008100348.o7A3mVG7009468@greed.delorie.com> To: gcc-patches@gcc.gnu.org Date: Mon, 9 Aug 2010 23:48:31 -0400 From: DJ Delorie List-Id: 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 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 }