[Bug c++/71283] Inconsistent location for C++ warning options in the manual
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71283 Eric Gallager changed: What|Removed |Added CC||fw at gcc dot gnu.org --- Comment #18 from Eric Gallager --- Florian Weimer was wondering about this general issue (of inconsistency in location of documentation for common C/C++ options) on the mailing lists recently: https://gcc.gnu.org/pipermail/gcc/2023-October/242669.html
[Bug c++/71283] Inconsistent location for C++ warning options in the manual
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71283 Barry Revzin changed: What|Removed |Added CC||barry.revzin at gmail dot com --- Comment #17 from Barry Revzin --- (In reply to Andrew Pinski from comment #2) > That is because this is C++ only option. It is listed under > https://gcc.gnu.org/onlinedocs/gcc-6.1.0/gcc/C_002b_002b-Dialect-Options. > html#C_002b_002b-Dialect-Options : > > -Wno-terminate (C++ and Objective-C++ only) > Disable the warning about a throw-expression that will immediately result in > a call to terminate. > > This is exact location for all other C++ only options are located. > > So not a bug. Sure, but right now some warnings are under Warning Options and others are under Dialect Options. I would never think to look for warnings under dialect options, since my initial thought would be that the latter is for the kinds of things that show up first on that page... -fabi-version, -fchar8_t, etc. You have to go pretty far down that page to get to warnings. -Wsuggest-override used to be under Warning Options, was recently moved to Dialect Options for instance. I would like to request that either all the warning options are documented under warning options, or that there is one page for all the C++ warning options (as distinct from "dialect options"), or something else along those lines. The current split is a bit confusing and makes it hard to find warnings.
[Bug c++/71283] Inconsistent location for C++ warning options in the manual
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71283 --- Comment #16 from Martin Liška --- (In reply to Eric Gallager from comment #15) > @marxin: does your porting of GCC documentation to sphinx address this issue > at all? If I see correctly, it's not addressed. The C++ options are listed at the following 2 pages: https://splichal.eu/gccsphinx-final/html/gcc/gcc-command-options/options-controlling-c%2B%2B-dialect.html https://splichal.eu/gccsphinx-final/html/gcc/gcc-command-options/options-to-request-or-suppress-warnings.html What's new that I generated entry for e.g.: -Wno-format Default option value for -Wformat.
[Bug c++/71283] Inconsistent location for C++ warning options in the manual
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71283 Eric Gallager changed: What|Removed |Added CC||marxin at gcc dot gnu.org --- Comment #15 from Eric Gallager --- @marxin: does your porting of GCC documentation to sphinx address this issue at all?
[Bug c++/71283] Inconsistent location for C++ warning options in the manual
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71283 Jonathan Wakely changed: What|Removed |Added Target Milestone|9.5 |---
[Bug c++/71283] Inconsistent location for C++ warning options in the manual
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71283 Richard Biener changed: What|Removed |Added Target Milestone|9.4 |9.5 --- Comment #14 from Richard Biener --- GCC 9.4 is being released, retargeting bugs to GCC 9.5.
[Bug c++/71283] Inconsistent location for C++ warning options in the manual
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71283 Jakub Jelinek changed: What|Removed |Added Target Milestone|9.3 |9.4 --- Comment #13 from Jakub Jelinek --- GCC 9.3.0 has been released, adjusting target milestone.
[Bug c++/71283] Inconsistent location for C++ warning options in the manual
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71283 Martin Sebor changed: What|Removed |Added Status|ASSIGNED|NEW Assignee|msebor at gcc dot gnu.org |unassigned at gcc dot gnu.org --- Comment #12 from Martin Sebor --- I'm not working on this right now.
[Bug c++/71283] Inconsistent location for C++ warning options in the manual
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71283 Eric Gallager changed: What|Removed |Added CC||sandra at gcc dot gnu.org --- Comment #11 from Eric Gallager --- Martin, did you want to stay the assignee for this? Sandra seemed to want to address this bug here: https://gcc.gnu.org/ml/gcc-patches/2020-02/msg01522.html
[Bug c++/71283] Inconsistent location for C++ warning options in the manual
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71283 Jakub Jelinek changed: What|Removed |Added Target Milestone|9.2 |9.3 --- Comment #10 from Jakub Jelinek --- GCC 9.2 has been released.
[Bug c++/71283] Inconsistent location for C++ warning options in the manual
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71283 Jakub Jelinek changed: What|Removed |Added Target Milestone|9.0 |9.2 --- Comment #9 from Jakub Jelinek --- GCC 9.1 has been released.
[Bug c++/71283] Inconsistent location for C++ warning options in the manual
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71283 Jonathan Wakely changed: What|Removed |Added CC||bugzilla@poradnik-webmaster ||a.com --- Comment #8 from Jonathan Wakely --- *** Bug 87684 has been marked as a duplicate of this bug. ***
[Bug c++/71283] Inconsistent location for C++ warning options in the manual
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71283 Martin Liška changed: What|Removed |Added CC||marxin at gcc dot gnu.org Target Milestone|--- |9.0
[Bug c++/71283] Inconsistent location for C++ warning options in the manual
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71283 --- Comment #7 from Eric Gallager --- (In reply to Martin Sebor from comment #6) > I'm trying to fix this for GCC 8. GCC 8 has been released. Deferred for GCC 9 then?
[Bug c++/71283] Inconsistent location for C++ warning options in the manual
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71283 Martin Sebor changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |msebor at gcc dot gnu.org --- Comment #6 from Martin Sebor --- I'm trying to fix this for GCC 8.
[Bug c++/71283] Inconsistent location for C++ warning options in the manual
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71283 Martin Sebor changed: What|Removed |Added Status|NEW |ASSIGNED
[Bug c++/71283] Inconsistent location for C++ warning options in the manual
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71283 Eric Gallager changed: What|Removed |Added CC||egallager at gcc dot gnu.org, ||msebor at gcc dot gnu.org --- Comment #5 from Eric Gallager --- Martin Sebor brought this up on the mailing lists here: https://gcc.gnu.org/ml/gcc/2018-04/msg00021.html
[Bug c++/71283] Inconsistent location for C++ warning options in the manual
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71283 Manuel López-Ibáñez changed: What|Removed |Added Keywords||easyhack Status|RESOLVED|NEW Last reconfirmed||2016-05-26 CC||manu at gcc dot gnu.org Resolution|INVALID |--- Summary|-Wterminate is not |Inconsistent location for |described in "Options to|C++ warning options in the |Request or Suppress |manual |Warnings" | Ever confirmed|0 |1 --- Comment #4 from Manuel López-Ibáñez --- (In reply to Eric Gallager from comment #3) > There are other C++-only options under "Options to Request or Suppress > Warnings". > For example: > * -Wc++11-compat > * -Wc++14-compat > * -Wconditionally-supported > * -Wno-conversion-null > * -Wzero-as-null-pointer-constant > * -Wsubobject-linkage > * -Wdelete-incomplete > * -Wuseless-cast > * -Wsized-deallocation > * -Wno-invalid-offsetof > > It's kind of inconsistent whether C++-only warnings are listed here or there. The perfect solution would be to move the options documentation to the *.opt files where they are defined and auto-generate the corresponding parts of the *.texi files from the *.opt files. This way the documentation would be much more consistent. This is similar to what we already do for target-hooks: see gcc/target.def That would be a very nice little project for a newbie. The short-term solution is for someone to propose patches to move those to the correct place: https://gcc.gnu.org/wiki/GettingStarted#Basics:_Contributing_to_GCC_in_10_easy_steps
