From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: sparclinux@vger.kernel.org
Subject: Re: sparc gcc 7.1 compile issue
Date: Mon, 19 Jun 2017 06:54:15 +0000 [thread overview]
Message-ID: <20170619065415.GC28760@physik.fu-berlin.de> (raw)
In-Reply-To: <20170531193431.GA26922@waldemar-brodkorb.de>
Hi Eric!
On Mon, Jun 19, 2017 at 08:47:47AM +0200, Eric Botcazou wrote:
> The Solaris maintainer ported Cilk++ (https://en.wikipedia.org/wiki/Cilk) to
> the SPARC architecture for GCC 7 and later, which explains why the issue
> doesn't show up with GCC 6. Cilk++ is a multithreading layer on top of C and
> C++ and its testsuite does a lot of thread manipulation.
>
> Note that, even when the machine doesn't freeze, the Cilk++ testsuite reports
> several timeouts (there are no such timeouts on Solaris):
> https://gcc.gnu.org/ml/gcc-testresults/2017-06/msg00462.html
Thanks for the explanation. We're now just disabling cilk on Debian
for gcc-7 and gcc-snapshot for the time being.
> This is probably the most promising angle of attack: someone should look into
> the timeouts by running the Cilk++ testsuite with low/no parallelism and find
> out where they come from (compiler, Cilk++ runtime or system/kernel). I can
> do it, but I'm essentially a compiler guy and I don't have much expertise in
> multithreading at the system/kernel level.
Ok, I hope that will help the kernel guys to figure out what the
problem is.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2017-06-19 6:54 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 19:34 sparc gcc 7.1 compile issue Waldemar Brodkorb
2017-05-31 19:34 ` Waldemar Brodkorb
2017-05-31 21:10 ` David Miller
2017-05-31 21:10 ` David Miller
2017-06-01 12:12 ` Waldemar Brodkorb
2017-06-01 12:12 ` Waldemar Brodkorb
2017-06-01 12:46 ` Anatoly Pugachev
2017-06-01 12:46 ` Anatoly Pugachev
2017-06-01 12:48 ` John Paul Adrian Glaubitz
2017-06-01 12:48 ` John Paul Adrian Glaubitz
2017-06-01 16:45 ` David Miller
2017-06-01 16:45 ` David Miller
2017-06-02 9:17 ` John Paul Adrian Glaubitz
2017-06-02 9:17 ` John Paul Adrian Glaubitz
2017-06-02 14:22 ` David Miller
2017-06-02 14:22 ` David Miller
2017-06-02 16:33 ` John Paul Adrian Glaubitz
2017-06-02 16:33 ` John Paul Adrian Glaubitz
2017-06-02 17:28 ` David Miller
2017-06-02 17:28 ` David Miller
2017-06-04 13:16 ` John Paul Adrian Glaubitz
2017-06-04 13:16 ` John Paul Adrian Glaubitz
2017-06-04 14:40 ` Waldemar Brodkorb
2017-06-04 14:40 ` Waldemar Brodkorb
2017-06-04 15:09 ` John Paul Adrian Glaubitz
2017-06-04 15:09 ` John Paul Adrian Glaubitz
2017-06-04 20:22 ` David Miller
2017-06-04 20:22 ` David Miller
2017-06-04 20:27 ` John Paul Adrian Glaubitz
2017-06-04 20:27 ` John Paul Adrian Glaubitz
2017-06-04 20:21 ` David Miller
2017-06-04 20:21 ` David Miller
2017-06-04 20:26 ` John Paul Adrian Glaubitz
2017-06-04 20:26 ` John Paul Adrian Glaubitz
2017-06-04 20:30 ` David Miller
2017-06-04 20:30 ` David Miller
2017-06-04 20:33 ` John Paul Adrian Glaubitz
2017-06-04 20:33 ` John Paul Adrian Glaubitz
2017-06-04 20:34 ` David Miller
2017-06-04 20:34 ` David Miller
2017-06-04 20:38 ` John Paul Adrian Glaubitz
2017-06-04 20:38 ` John Paul Adrian Glaubitz
2017-06-18 9:22 ` Pavel Machek
2017-06-18 9:22 ` Pavel Machek
2017-06-18 19:59 ` John Paul Adrian Glaubitz
2017-06-18 22:42 ` John Paul Adrian Glaubitz
2017-06-19 1:42 ` David Miller
2017-06-19 6:47 ` Eric Botcazou
2017-06-19 6:54 ` John Paul Adrian Glaubitz [this message]
2017-06-23 17:50 ` Eric Botcazou
2017-06-23 18:46 ` David Miller
2017-06-23 19:18 ` Eric Botcazou
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=20170619065415.GC28760@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=sparclinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.