From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id BD153385EC58; Sun, 26 Jul 2020 15:51:06 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BD153385EC58 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1595778666; bh=PnDXArM0uU6usGz6+22U0TidL0oqGcDVSVlCevnvxFY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=QnlxJS6RXlWU1fGrgFiV6lRLJymXyegkzJNr1wmYXPBJDqkNTU5MBfMIYR4Rb6Xo9 Mwo/8ozRrzuxi1lYiEVtdhrRNV2di9/4E9t1eS5IZop65bKibPyt4bEEkuF479lZfc 8LZ1FBRRUQAq4AzNWNIisBGsKFmz+htm3AuwTk8U= From: "mark at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/70611] Compiling binutils with -flto -Wstack-usage fails. Date: Sun, 26 Jul 2020 15:51:06 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: lto X-Bugzilla-Version: 5.3.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mark at gcc dot gnu.org X-Bugzilla-Status: REOPENED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Jul 2020 15:51:06 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D70611 --- Comment #6 from Mark Wielaard --- (In reply to Mark Wielaard from comment #5) > This is also one of the issues that prevent elfutils to build with LTO. > The workaround is to compile with -Wno-error=3Dstack-usage=3D added to CF= LAGS: > https://sourceware.org/pipermail/elfutils-devel/2020q2/002733.html Sorry, commented on the wrong bug, the above was meant for bug #93865=