public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "yannick_duchene at yahoo dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/46189] New: Oudated item in GNAT documentation
Date: Tue, 26 Oct 2010 18:50:00 -0000 [thread overview]
Message-ID: <bug-46189-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46189
Summary: Oudated item in GNAT documentation
Product: gcc
Version: 4.5.0
URL: http://www.adacore.com/wp-content/files/auto_update/gn
at-unw-docs/html/gnat_ugn_24.html
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ada
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: yannick_duchene@yahoo.fr
CC: ludovic@ludovic-brenta.org
On the page
http://www.adacore.com/wp-content/files/auto_update/gnat-unw-docs/html/gnat_ugn_24.html
the GNAT documentation makes mention of an “-fstack-usage” option which intent
is to provide static stack analysis. But this options seems not to be there any
more, at least with the GNAT front-end which comes with GCC 4.5.0.
Some talks on miscellaneous forums and Usenet thread, also suggest this is also
no more available for GCC too (although the incriminated document is a GNAT
document).
May be this reference to the “-fstack-usage” option should be removed from
documentations in order to not confuse users.
next reply other threads:[~2010-10-26 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 18:50 yannick_duchene at yahoo dot fr [this message]
2010-10-26 18:52 ` [Bug ada/46189] " pinskia at gcc dot gnu.org
2010-10-26 20:25 ` ebotcazou at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-46189-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).