From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28983 invoked by alias); 26 Apr 2017 21:27:37 -0000 Mailing-List: contact binutils-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sourceware.org Received: (qmail 28965 invoked by uid 89); 26 Apr 2017 21:27:37 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: =?ISO-8859-1?Q?No, score=2.3 required=5.0 tests=AWL,BAYES_00,BODY_8BITS,FREEMAIL_FROM,GARBLED_BODY,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=H*Ad:U*amodra, =d0=b8=d0=bb=d1?= X-HELO: mail-yb0-f174.google.com Received: from mail-yb0-f174.google.com (HELO mail-yb0-f174.google.com) (209.85.213.174) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 26 Apr 2017 21:27:35 +0000 Received: by mail-yb0-f174.google.com with SMTP id 8so3573149ybw.1 for ; Wed, 26 Apr 2017 14:27:37 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=Tjw+biTz7jA7IZtWF70B1Dr82ePE2I5Gvx7kSRKluUk=; b=BnsbuSjTYsxqMgjZpfXjUtlM36UcA9LeZkHnSjHK3lnrrSxTevlxoUcOna8cAKtH5e W8LqCqQlDSpuof1u5CfsRJnTl7N6bf5xKZAmbqHRt54jraQ6RcWzLZa6HwZTCW9M+rlX HcGtjh/yHBegxZjowOUBq8O9aH2GEA+zuVJnVCyijoLGDl3tc/itdkC3alLrsm48p5Mt AXjXfvQJNl4nmGCBynUey87+tXc18ZBOu7x88j3b8i3wUj7H5X9WDmfxlRoPkX3/kaZd OoRFDkwL+w+YTD2gfz0MAtsCMEt2uL0smUNuWbhkPTJkjN+3QNyWbZ+dELbA8oMlzwhl JBTg== X-Gm-Message-State: AN3rC/6XD+VbxHpM5A5cwoPTPLdx/BB73ot86JmZdRulg159zWIZqpje SC3uMFDbZR36WGfy1LYzRmEVdpB5Og== X-Received: by 10.37.74.199 with SMTP id x190mr1652784yba.138.1493242056266; Wed, 26 Apr 2017 14:27:36 -0700 (PDT) MIME-Version: 1.0 Received: by 10.129.121.71 with HTTP; Wed, 26 Apr 2017 14:27:35 -0700 (PDT) In-Reply-To: <81e2a959-b808-829f-d139-fd6ec0ae5845@aegee.org> References: <2149d70f-e3dd-3881-e809-bf1921528100@aegee.org> <20170424065848.GO24006@bubble.grove.modra.org> <81e2a959-b808-829f-d139-fd6ec0ae5845@aegee.org> From: Andrew Pinski Date: Wed, 26 Apr 2017 21:27:00 -0000 Message-ID: Subject: Re: building in dedicated directory; binutils -Wstack-usage and -flto To: =?UTF-8?B?0JTQuNC70Y/QvSDQn9Cw0LvQsNGD0LfQvtCy?= Cc: Alan Modra , binutils Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2017-04/txt/msg00248.txt.bz2 On Wed, Apr 26, 2017 at 2:21 PM, =D0=94=D0=B8=D0=BB=D1=8F=D0=BD =D0=9F=D0= =B0=D0=BB=D0=B0=D1=83=D0=B7=D0=BE=D0=B2 wrote: > Hello, > > I guess most binutils developers use separate build directory, because th= ey > were told to do so. This a chicken-egg-problem. One reason why people using separate build directories to build a few different targets and versions of binutils (cross, native, candian cross). Thanks, Andrew > > Can you ensure that "make distclean" cleans everything created by "make" > (e.g. in the separate build directory)? > > Is the message "error: stack usage might be unbounded > [-Werror=3Dstack-usage=3D]", when binutils is -flto built, correct (lto u= ses > more stack), or wrong (liblto_plugin or ld handle it wrong). > > Regards > =D0=94=D0=B8=D0=BB=D1=8F=D0=BD > > > On 04/24/2017 08:58 AM, Alan Modra wrote: >> >> On Sun, Apr 23, 2017 at 04:33:16PM +0200, =D0=94=D0=B8=D0=BB=D1=8F=D0=BD= =D0=9F=D0=B0=D0=BB=D0=B0=D1=83=D0=B7=D0=BE=D0=B2 wrote: >>> >>> searching for "binutils build dedicated directory" the answers is "the >>> binutils documentation recommends building binutils in a dedicated build >>> directory", >>> >>> What is the reasoning for this, except that "make distclean" does not >>> clean >>> everything, as it should? >> >> >> If we did a poll of binutils developers, I'd guess that most use a >> separate build directory. It's likely that builds in the source >> directory are not so well tested.. >> >>> lto1: all warnings being treated as errors >> >> [snip] >>> >>> Please make binutils build with -flto? >> >> >> configure with --disable-werror. >> >