From: Daniel Santos <daniel.santos@pobox.com>
To: Bernd Edlinger <bernd.edlinger@hotmail.de>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] [i386] Recompute the frame layout less often
Date: Thu, 18 May 2017 07:14:00 -0000 [thread overview]
Message-ID: <b3626606-c3e6-4147-0fa7-1abe2cc508d8@pobox.com> (raw)
In-Reply-To: <AM4PR0701MB2162A2C53C8BCBEF2FD2ECF6E4E70@AM4PR0701MB2162.eurprd07.prod.outlook.com>
On 05/17/2017 01:39 PM, Bernd Edlinger wrote:
> On 05/15/17 03:39, Daniel Santos wrote:
>
>> I should add that if you want to run faster tests just on the ms to sysv
>> abi code, you can use make RUNTESTFLAGS="ms-sysv.exp" check and then if
>> that succeeds run the full testsuite.
>>
>> Daniel
> Hmm, that's funny...
>
> If I use "make check-c RUNTESTFLAGS="ms-sysv.exp" -j8" it seems to work,
> but if I omit the -j8 it fails:
>
> make check-c RUNTESTFLAGS="ms-sysv.exp"
> ...Test Run By ed on Wed May 17 20:38:24 2017
> Native configuration is x86_64-pc-linux-gnu
>
> === gcc tests ===
>
> Schedule of variations:
> unix
>
> Running target unix
> Using /usr/share/dejagnu/baseboards/unix.exp as board description file
> for target.
> Using /usr/share/dejagnu/config/unix.exp as generic interface file for
> target.
> Using /home/ed/gnu/gcc-trunk/gcc/testsuite/config/default.exp as
> tool-and-target-specific interface file.
> Running
> /home/ed/gnu/gcc-trunk/gcc/testsuite/gcc.target/x86_64/abi/ms-sysv/ms-sysv.exp
> ...
> ERROR: tcl error sourcing
> /home/ed/gnu/gcc-trunk/gcc/testsuite/gcc.target/x86_64/abi/ms-sysv/ms-sysv.exp.
> ERROR: no such variable
> (read trace on "env(GCC_RUNTEST_PARALLELIZE_DIR)")
> invoked from within
> "set parallel_dir "$env(GCC_RUNTEST_PARALLELIZE_DIR)/abi-ms-sysv""
> (file
> "/home/ed/gnu/gcc-trunk/gcc/testsuite/gcc.target/x86_64/abi/ms-sysv/ms-sysv.exp"
> line 154)
> invoked from within
> "source
> /home/ed/gnu/gcc-trunk/gcc/testsuite/gcc.target/x86_64/abi/ms-sysv/ms-sysv.exp"
> ("uplevel" body line 1)
> invoked from within
> "uplevel #0 source
> /home/ed/gnu/gcc-trunk/gcc/testsuite/gcc.target/x86_64/abi/ms-sysv/ms-sysv.exp"
> invoked from within
> "catch "uplevel #0 source $test_file_name""
>
> === gcc Summary ===
>
> /home/ed/gnu/gcc-build/gcc/xgcc version 8.0.0 20170514 (experimental)
> (GCC)
>
> make[2]: Leaving directory `/home/ed/gnu/gcc-build/gcc'
> make[1]: Leaving directory `/home/ed/gnu/gcc-build/gcc'
Hmm, that might be something I hadn't actually tried. And if I run it
in a directory where I had previously run a multi-job check it doesn't
blow up (maybe because the directory is already there?) Due to the
nature of my test program, I had to break with tradition and implement
something akin to the test that generates random structs (I forgot what
that one is called). It ended up breaking the bastardized
parallelization scheme, so I had to implement my own re-bastardized
scheme. Looks like I can just skip parallelization if
GCC_RUNTEST_PARALLELIZE_DIR isn't defined.
I have another Solaris test issue on PR 80759 so I'll fix that along
with it.
Thanks,
Daniel
PS: Oh! it might be due to the difference between -j1 and no -j argument.
next prev parent reply other threads:[~2017-05-18 7:09 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-14 9:11 Bernd Edlinger
2017-05-14 9:58 ` Daniel Santos
2017-05-14 10:27 ` Uros Bizjak
2017-05-14 18:11 ` Bernd Edlinger
2017-05-14 20:37 ` Daniel Santos
2017-05-15 2:23 ` Daniel Santos
2017-05-15 20:41 ` Bernd Edlinger
2017-05-15 23:52 ` Daniel Santos
2017-05-16 5:42 ` Daniel Santos
2017-05-16 8:52 ` Bernd Edlinger
2017-05-16 15:11 ` Daniel Santos
2017-05-16 17:38 ` Ian Lance Taylor via gcc-patches
2017-05-16 20:10 ` Bernd Edlinger
2017-05-16 21:05 ` Bernd Edlinger
2017-05-17 2:12 ` Daniel Santos
2017-05-17 17:43 ` Bernd Edlinger
2017-05-18 7:05 ` Daniel Santos
2017-05-18 13:48 ` Bernd Edlinger
2017-05-19 3:13 ` Daniel Santos
2017-05-22 18:32 ` Bernd Edlinger
2017-05-23 14:34 ` Bernd Edlinger
2017-05-24 6:49 ` Daniel Santos
2017-06-01 16:06 ` [PING][PATCH] " Bernd Edlinger
2017-06-01 18:18 ` [PATCH] " Uros Bizjak
2017-05-23 23:01 ` Daniel Santos
2017-05-16 21:35 ` Daniel Santos
2017-05-17 18:41 ` Bernd Edlinger
2017-05-18 7:14 ` Daniel Santos [this message]
2017-05-19 5:12 ` Daniel Santos
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=b3626606-c3e6-4147-0fa7-1abe2cc508d8@pobox.com \
--to=daniel.santos@pobox.com \
--cc=bernd.edlinger@hotmail.de \
--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).