public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Gaius Mulley <gaius@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-5130] Testsuite: use same timeout for gm2 as other front-ends Date: Thu, 12 Jan 2023 23:49:43 +0000 (GMT) [thread overview] Message-ID: <20230112234943.D3D483858418@sourceware.org> (raw) https://gcc.gnu.org/g:c0597d81b13c0cac41a9381fc5f3e6c73aa2ccaf commit r13-5130-gc0597d81b13c0cac41a9381fc5f3e6c73aa2ccaf Author: Gaius Mulley <gaiusmod2@gmail.com> Date: Thu Jan 12 23:48:48 2023 +0000 Testsuite: use same timeout for gm2 as other front-ends Committing a patch authored by: Jason Merrill <jason@redhat.com> which enables timeouts in the gm2 regression script library gm2.exp. gcc/testsuite/ChangeLog: * lib/gm2.exp: Use timeout.exp. Signed-off-by: Gaius Mulley <gaiusmod2@gmail.com> Diff: --- gcc/testsuite/lib/gm2.exp | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/gcc/testsuite/lib/gm2.exp b/gcc/testsuite/lib/gm2.exp index a2169b95279..0d8490c6849 100644 --- a/gcc/testsuite/lib/gm2.exp +++ b/gcc/testsuite/lib/gm2.exp @@ -22,7 +22,7 @@ load_lib libgloss.exp load_lib prune.exp load_lib gcc-defs.exp load_lib target-libpath.exp - +load_lib timeout.exp # # GCC_UNDER_TEST is the compiler under test. @@ -183,9 +183,7 @@ proc gm2_target_compile_default { source dest type options } { if [info exists TOOL_OPTIONS] { lappend options "additional_flags=$TOOL_OPTIONS" } - if [target_info exists gcc,timeout] { - lappend options "timeout=[target_info gcc,timeout]" - } + lappend options "timeout=[timeout_value]" lappend options "compiler=$GCC_UNDER_TEST" # puts stderr "options = $options\n" # puts stderr "***** target_compile: $source $dest $type $options\n"
reply other threads:[~2023-01-12 23:49 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230112234943.D3D483858418@sourceware.org \ --to=gaius@gcc.gnu.org \ --cc=gcc-cvs@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: linkBe 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).