public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
* [Bug ada/46189] New: Oudated item in GNAT documentation @ 2010-10-26 18:50 yannick_duchene at yahoo dot fr 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 0 siblings, 2 replies; 3+ messages in thread From: yannick_duchene at yahoo dot fr @ 2010-10-26 18:50 UTC (permalink / raw) To: gcc-bugs 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. ^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug ada/46189] Oudated item in GNAT documentation 2010-10-26 18:50 [Bug ada/46189] New: Oudated item in GNAT documentation yannick_duchene at yahoo dot fr @ 2010-10-26 18:52 ` pinskia at gcc dot gnu.org 2010-10-26 20:25 ` ebotcazou at gcc dot gnu.org 1 sibling, 0 replies; 3+ messages in thread From: pinskia at gcc dot gnu.org @ 2010-10-26 18:52 UTC (permalink / raw) To: gcc-bugs http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46189 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> 2010-10-26 18:52:22 UTC --- fstack-usage was added on the trunk (for 4.6.0). ^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug ada/46189] Oudated item in GNAT documentation 2010-10-26 18:50 [Bug ada/46189] New: Oudated item in GNAT documentation yannick_duchene at yahoo dot fr 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 1 sibling, 0 replies; 3+ messages in thread From: ebotcazou at gcc dot gnu.org @ 2010-10-26 20:25 UTC (permalink / raw) To: gcc-bugs http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46189 Eric Botcazou <ebotcazou at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ebotcazou at gcc dot | |gnu.org --- Comment #2 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2010-10-26 20:24:52 UTC --- > 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. Please do not report issues related to GNAT Pro here. GNAT Pro is a separate product released by AdaCore whereas this is bugzilla for the FSF GNAT compiler. ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2010-10-26 20:25 UTC | newest] Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2010-10-26 18:50 [Bug ada/46189] New: Oudated item in GNAT documentation yannick_duchene at yahoo dot fr 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
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).