From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: a07f3367d7,233c88e0e480e0b X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,UTF8 Path: g2news1.google.com!news4.google.com!news3.google.com!proxad.net!feeder1-2.proxad.net!newsfeed.straub-nv.de!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail From: Ludovic Brenta Newsgroups: comp.lang.ada Subject: Re: GNAT/GCC and -fstack-check Date: Tue, 26 Oct 2010 20:19:11 +0200 Organization: A noiseless patient Spider Message-ID: <87k4l4rf4w.fsf@ludovic-brenta.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: mx01.eternal-september.org; posting-host="KBntBobxUBwFAI9HxLARgQ"; logging-data="22747"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+WjM9JdhWQCidtJtYks8tg" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) Cancel-Lock: sha1:avdJQa5qJwEWiqqEf0gJ4QZkW8o= sha1:GKeUPw5FEKbFqoyEibkmiRNx2Bc= Xref: g2news1.google.com comp.lang.ada:14806 Date: 2010-10-26T20:19:11+02:00 List-Id: Yannick Duchêne writes on comp.lang.ada > Le Mon, 25 Oct 2010 22:15:21 +0200, Yannick Duchêne (Hibou57) > a écrit: > > By the way, the GNAT documentation about stack analysis and handling > seems a bit outdated. It talks about an “-fstack-usage” option, which > does not seems to be recognized (gnatmake complains “invalid switch: > -fstack-usage”). Some web-talks about this option strictly concerning > GCC says it is not neither supported by GCC anymore. I suggest you report this as a documentation bug. > I am talking about this option, because I attempted to use it to check > if something is really wrong with the stack. > > Note that I did not get the error from “-fstack-check” with the GCC > 3.x of GNAT 2010. That would be 4.3.x, of course. And the error from "-fstack-check" depends on a complex set of conditions. -- Ludovic Brenta.