search for: j16

Hi, Currently the first stage ("run sanitizer tests in gcc build") of the sanitizer-ppc64-linux1 buildbot is only failing because of: + cd clang_build + make -j16 check-lsan make: *** No rule to make target `check-lsan'. Stop. + echo @@@STEP_FAILURE@@@ @@@STEP_FAILURE@@@ + cd clang_build + make -j16 check-msan make: *** No rule to make target `check-msan'. Stop. + echo @@@STEP_FAILURE@@@ @@@STEP_FAILURE@@@ + cd clang_build + make -j16 check-tsan ma...

...t 3:15:27 PM Jay Foad <jay.foad at gmail.com> wrote: >> >> Hi, >> >> Currently the first stage ("run sanitizer tests in gcc build") of the >> sanitizer-ppc64-linux1 buildbot is only failing because of: >> >> + cd clang_build >> + make -j16 check-lsan >> make: *** No rule to make target `check-lsan'. Stop. >> + echo @@@STEP_FAILURE@@@ >> @@@STEP_FAILURE@@@ >> + cd clang_build >> + make -j16 check-msan >> make: *** No rule to make target `check-msan'. Stop. >> + echo @@@STEP_FAILURE@@...

...l > translation unit needs to be compiled into a small executable (no long > compiler/linker waits) it may be possible but, again, it only speaks > about the relative sizes of LLVM/Cray's compiler. Ok, here are some hard numbers for empty builds: LLVM empty build: /usr/bin/time make -j16 4.32user 2.47system 0:03.21elapsed 211%CPU (0avgtext+0avgdata 13376maxresident)k 0inputs+0outputs (0major+671804minor)pagefaults 0swaps Cray empty build: /usr/bin/time make dynamic-developer -j16 2.88user 1.06system 0:04.94elapsed 79%CPU (0avgtext+0avgdata 64208maxresident)k 0inputs+0outputs (0maj...

Nico Weber <thakis at chromium.org> writes: > On Tue, Nov 1, 2011 at 3:09 PM, David A. Greene <greened at obbligato.org> wrote: >> Óscar Fuentes <ofv at wanadoo.es> writes: >> >>> Okay, we can get rid of recursive make. However, as pointed out >>> elsewhere, removing recursive make will not make a difference on the >>> LLVM build. What

...error: linker command failed due to signal (use -v to see invocation) [32/492] Building CXX object tools/llvm-cov/CMakeFiles/llvm-cov.dir/gcov.cpp.o As reported on Discord, switching back to ld works around this issue. On my system a process gets a 6 GB of memory max can be used, and I use ninja -j16. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200203/dcc39115/attachment.html>

On Sun, Sep 18, 2016 at 12:32 AM, Mehdi Amini <mehdi.amini at apple.com> wrote: > >> On Sep 17, 2016, at 3:19 PM, Carsten Mattner <carstenmattner at gmail.com> wrote: >> >> So, when I embark on the next ThinLTO try build, probably this Sunday, >> should I append -Wl,-plugin-opt,jobs=NUM_PHYS_CORES to LDFLAGS >> and run ninja without -j or

greened at obbligato.org (David A. Greene) writes: > Ok, here are some hard numbers for empty builds: > > LLVM empty build: > /usr/bin/time make -j16 > 4.32user 2.47system 0:03.21elapsed 211%CPU (0avgtext+0avgdata 13376maxresident)k > 0inputs+0outputs (0major+671804minor)pagefaults 0swaps So your 16-way machine takes 2.5 times more than my 4-way cheap desktop... > Cray empty build: > /usr/bin/time make dynamic-developer -j16 > 2...

...ect > independently. > > The "3rd approach" here is the 1st solution in my original proposal. Almost > all coworkers call it sucks:-) > Now I accept it because the it has no way to be adaptive. > > Consider the scenario we compile the llvm compiler. We use "make -j16" for > computer with 8 processor, each make-thread invoke a compiler which may > blindly invoke 16 threads! > So, we end up to have 16*16 threads. > Determining the right parallelism is not the job of the compiler (builtin) nor that of a developer -- the underlying build system sh...

The test relies on the timeout program. Also, since the nbdkit_nanosleep code relies on the Linux extension POLLRDHUP to detect early client closure, we may have to relax that part of the test when porting to platforms that lack ppoll/POLLRDHUP. (That is, while we should still be able to let a signal to the server shut down nbdkit quickly, it's harder to let a client close()ing its end cause

...ith lots of errors. > This must be a problem with my build, then, but since this is a fresh > tarball I am a bit puzzled. > > I would appreciate some hint on where to start looking for any mistake. > > My environment: > Fedora 28 > ./configure --enable-selftest > make -j16 > make test > > All run as the ordinary user - I understand from the 2012 talk that > 'root' privileges should not be needed. Do I get this wrong? Root privileges are not required. While 'make test' is intended to pass generally, the reference environment is Ubuntu 1...

...aches to build the post-ipo object independently. The "3rd approach" here is the 1st solution in my original proposal. Almost all coworkers call it sucks:-) Now I accept it because the it has no way to be adaptive. Consider the scenario we compile the llvm compiler. We use "make -j16" for computer with 8 processor, each make-thread invoke a compiler which may blindly invoke 16 threads! So, we end up to have 16*16 threads. Being adaptive will render it possible to pick up right factor judiciously and adpatively. In any case, I will support this approach (i.e. the 3rd ap...

Hi all, I just downloaded a fresh samba-4.10.0 tarball to verify the result of 'make test' What I did is: ./configure --enable-selftest make make test All run as the ordinary user. I encountered a build problem with 'make' in source4/lib/messaging/messaging_handlers.c due to the following conditional being placed /before/ #include "includes.h" #if defined(DEVELOPER)

On Apr 30, 2008, at 8:51 PM, David Vandevoorde wrote: >> This isn't safe in general unless you can (tightly) bound "n". You >> don't want to overflow the stack. > > Ah yes, of course. Does LLVM do this for known & small constant n? We don't do this currently, primarily because I haven't seen a case where it is a win yet: it would be very easy to

A third approach is to decouple the backend compilation and parallelism strategy from the partitioning. The partitioning can spits out partition BC files and some action records in some standard format. All of this can be fed into some driver tools that converts the compilation action file into make/build file of the underlying build system of your choice: 1) it can simply a compiler driver that

Just to follow-up, I'm now encountering this as well. I'm doing this on Linux. It seems that when linking with the most-recently built clang, the unit tests are taking a while to complete. It's notably not using more than 1 thread, and if using `lld` I would have expected the linker to still be running in parallel. I'm doing this on a debug build, so that might help narrow it

...cceed? My bigger problem is that it failed with lots of errors. This must be a problem with my build, then, but since this is a fresh tarball I am a bit puzzled. I would appreciate some hint on where to start looking for any mistake. My environment: Fedora 28 ./configure --enable-selftest make -j16 make test All run as the ordinary user - I understand from the 2012 talk that 'root' privileges should not be needed. Do I get this wrong? Thanks in advance, Manfred On 4/1/2019 8:03 PM, Andrew Bartlett wrote: > On Mon, 2019-04-01 at 17:08 +0200, Manfred via samba wrote: >> H...

I've been thinking recently that we should re-enable DIR_INDEX in mke2fs by default. When it first came out, we had done this and were bitten by a few bugs in the code. However, this code has been in heavy use for several thousand filesystem years in Lustre, if not elsewhere, and I'm inclined to think it is pretty safe these days. Likewise, RHEL/FC have had RESIZE_INODE as a standard

...17.23 MiB/s, done. Resolving deltas: 100% (51319/51319), done. [djm at djm-desktop tmp]$ cd openssh-portable [djm at djm-desktop openssh-portable]$ patch -sp1 < /tmp/match.diff [djm at djm-desktop openssh-portable]$ autoreconf [djm at djm-desktop openssh-portable]$ ./configure && make -j16 ... [djm at djm-desktop openssh-portable]$ echo $? 0 [djm at djm-desktop openssh-portable]$ ./ssh -V OpenSSH_9.7p1, OpenSSL 3.0.10 1 Aug 2023 -------------- next part -------------- diff --git a/readconf.c b/readconf.c index 3a64a0441..dff6a9df6 100644 --- a/readconf.c +++ b/readconf.c @@ -70,6 +70...

... and I guess your next question will be about compilation environment, so: ``` $ gcc --version gcc (Gentoo 13.2.1_p20240210 p14) 13.2.1 20240210 Copyright (C) 2023 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. ``` I'm running on gentoo. I tested that the

Try as I might I can't seem to get LLVM to bulid using clang/clang++. No matter what I do it insists on using /usr/bin/cc and /usr/bin/c++ which are gcc. Am I missing something obvious? I vaguely remember some document describing a stage1 compiler built by your old toolchain and a stage2 compiler but I can't find the steps to do that any more. $ CC=/usr/local/bin/clang