search for: jureca

Displaying 4 results from an estimated 4 matches for "jureca".

2020 Apr 02
2
LLD issue on a massively parallel build machine
...taru.kitayama at gmail.com> > Cc: Nemanja Ivanovic via llvm-dev <llvm-dev at lists.llvm.org> > Subject: Re: [llvm-dev] LLD issue on a massively parallel build machine > > On 04/01/2020 04:12 PM, Itaru Kitayama wrote: > > On another login node which is 256 (GB)/48 (nodes) JURECA at JSC, I > never had an LLD issue without setting -j when executing ninja > > in the past few weeks. > > > > On Thu, Apr 2, 2020 at 7:17 AM Itaru Kitayama <itaru.kitayama at gmail.com > <mailto:itaru.kitayama at gmail.com>> wrote: > > > > Tom, &g...
2020 Apr 04
2
LLD issue on a massively parallel build machine
...Cc: Nemanja Ivanovic via llvm-dev <llvm-dev at lists.llvm.org> >> > Subject: Re: [llvm-dev] LLD issue on a massively parallel build machine >> > >> > On 04/01/2020 04:12 PM, Itaru Kitayama wrote: >> > > On another login node which is 256 (GB)/48 (nodes) JURECA at JSC, I >> > never had an LLD issue without setting -j when executing ninja >> > > in the past few weeks. >> > > >> > > On Thu, Apr 2, 2020 at 7:17 AM Itaru Kitayama < >> itaru.kitayama at gmail.com >> > <mailto:itaru.kitayama at g...
2020 Apr 01
2
LLD issue on a massively parallel build machine
On another login node which is 256 (GB)/48 (nodes) JURECA at JSC, I never had an LLD issue without setting -j when executing ninja in the past few weeks. On Thu, Apr 2, 2020 at 7:17 AM Itaru Kitayama <itaru.kitayama at gmail.com> wrote: > Tom, > Then what ratio do you think it’s minimal? > > On Thu, Apr 2, 2020 at 6:11 Tom Stellard &lt...
2020 Apr 01
2
LLD issue on a massively parallel build machine
On 04/01/2020 01:47 PM, Itaru Kitayama via llvm-dev wrote: > Thanks for the heads up the supercomputer > Is down for maintenance this week. > I’ll give it a try when it gets back. > This doesn't look to me like it's necessarily an lld issue. Trying to build all the sub-projects without limiting the number of ninja jobs is almost guaranteed to run out of memory on a machine