From owner-freebsd-toolchain@freebsd.org Thu Feb 28 02:31:16 2019 Return-Path: Delivered-To: freebsd-toolchain@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 539BD151131A for ; Thu, 28 Feb 2019 02:31:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id C522D70417 for ; Thu, 28 Feb 2019 02:31:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 7E8491511319; Thu, 28 Feb 2019 02:31:15 +0000 (UTC) Delivered-To: toolchain@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5752F1511314 for ; Thu, 28 Feb 2019 02:31:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E229F7040E for ; Thu, 28 Feb 2019 02:31:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 040FD11F6D for ; Thu, 28 Feb 2019 02:31:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x1S2VD78084791 for ; Thu, 28 Feb 2019 02:31:13 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x1S2VD0U084785 for toolchain@FreeBSD.org; Thu, 28 Feb 2019 02:31:13 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: toolchain@FreeBSD.org Subject: [Bug 236055] lang/gcc8 Linker command failed due to signal Date: Thu, 28 Feb 2019 02:31:13 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: marklmi26-fbsd@yahoo.com X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Not A Bug X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: toolchain@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2019 02:31:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D236055 Mark Millard changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marklmi26-fbsd@yahoo.com --- Comment #5 from Mark Millard --- (In reply to Ed Maste from comment #4) It would also help if the dmesg/console messages avoided incorrectly referencing "out of swap" when such need not be involved. Details follow, describing the current context. If the person with the problem see any of the: swap_pager_getswapspace(number): failed message they really were out of swap. But if they only see: kernel: pid ... (...), uid ..., was killed: out of swap space they likely had swap available, the issue not really being swap space. The 2nd type of message can happen when there is plenty of swap but processes that stay runnable are preventing having sufficient free RAM after some number of tries by FreeBSD: runnable processes are not (fully) swapped-out by FreeBSD, only paged. In my view the "was killed: out of swap space" should text be adjusted. Other notes: There is a tunable that can increase the number of tries at freeing RAM before "was killed: out of swap space" happens. This is used on low end armv7's and aarch64's and such to allow buildworld and the like to complete with -j4, for example. vm.pageout_oom_seq has a default of 12 (last I checked). Figures like 120 and 1024 have been used on those low end armv7 and aarch64 examples. (pi2 V1.1 and rpi3 are examples: just 1 GiByte of RAM. Of course sufficient swap space is also required for this kind of context.) For lld based links, LDFLAGS.lld+=3D -Wl,--no-threads can also help avoid memory use by avoiding having ncpu+2 threads in use in each active lld. How-to-build-software documentation should probably cover this subject. --=20 You are receiving this mail because: You are the assignee for the bug.=