From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 6F6BB385DC24; Fri, 17 Apr 2020 17:35:53 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6F6BB385DC24
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1587144953;
 bh=l0zXqGQ5xtUBZDhv/m/uJv8nLIR4tk9YpsXWx+Zd9e0=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=prhyh6jwHVaQ/7Ama2L0CFEwv5ZV5erx9EP8lGukViiF5GCrxgXmMg9pYglGN412/
 +uNoUPMJ/cBy/hMYTZRkh80yiOKFNb4RGQDzSjyOsv2Donn3AD+abK4Xrhv304ogQO
 qGpxMwrBsVX58Z+w+LWiB0KGrKOCx6YhV2Qt4cEU=
From: "Torsten at Robitzki dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/90983] manual documents `-Wno-stack-usage` flag, but it
 is unrecognized
Date: Fri, 17 Apr 2020 17:35:53 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 9.1.0
X-Bugzilla-Keywords: diagnostic, documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: Torsten at Robitzki dot de
X-Bugzilla-Status: NEW
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: <bug-90983-4-ANJrU2lTNd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90983-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90983-4@http.gcc.gnu.org/bugzilla/>
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 <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <http://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <http://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Apr 2020 17:35:53 -0000

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D90983

--- Comment #5 from Torsten Robitzki <Torsten at Robitzki dot de> ---
(In reply to Martin Sebor from comment #4)
> Using a very large -Wstack-usage argument should effectively disable the
> warning.  E.g., -Wstack-usage=3D4EiB or -Wstack-usage=3D$(getconf ULONG_M=
AX).

Unfortunately, not when the stack usage is reported as unbound:

    #include <alloca.h>

    int foo(int i)
    {
        void* p =3D alloca(i);

        return p !=3D 0;
    }

    int main()
    {
        foo(4000);
        return 0;
    }


    $ arm-none-eabi-gcc t.c -Wstack-usage=3D200 -Wstack-usage=3D4EiB
    t.c: In function 'foo':
    t.c:3:5: warning: stack usage might be unbounded [-Wstack-usage=3D]
        3 | int foo(int i)
          |     ^~~=