public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug tree-optimization/30334] [meta-bug] Request for -Wundefined
[not found] <bug-30334-4@http.gcc.gnu.org/bugzilla/>
@ 2020-04-13 20:27 ` msebor at gcc dot gnu.org
2020-04-13 21:15 ` msebor at gcc dot gnu.org
` (2 subsequent siblings)
3 siblings, 0 replies; 4+ messages in thread
From: msebor at gcc dot gnu.org @ 2020-04-13 20:27 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30334
Bug 30334 depends on bug 81172, which changed state.
Bug 81172 Summary: Expected new warning option -Warray-bounds-pointer-arithmetic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81172
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug tree-optimization/30334] [meta-bug] Request for -Wundefined
[not found] <bug-30334-4@http.gcc.gnu.org/bugzilla/>
2020-04-13 20:27 ` [Bug tree-optimization/30334] [meta-bug] Request for -Wundefined msebor at gcc dot gnu.org
@ 2020-04-13 21:15 ` msebor at gcc dot gnu.org
2020-04-14 6:07 ` egallager at gcc dot gnu.org
2023-05-16 17:40 ` pinskia at gcc dot gnu.org
3 siblings, 0 replies; 4+ messages in thread
From: msebor at gcc dot gnu.org @ 2020-04-13 21:15 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30334
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |msebor at gcc dot gnu.org
--- Comment #17 from Martin Sebor <msebor at gcc dot gnu.org> ---
I agree with the goal of detecting undefined behavior but I don't think a
catchall warning option like -Wundefined would be very helpful. Not all kinds
of undefined behavior are of the same severity so providing a single option for
all of it would make it hard to clean up code with more than just a handful of
instances of it. Especially for late warnings that are susceptible to false
positives, being able to control them in a targeted way is important.
The trend over the last years has been toward providing granular warning
options to control the detection of specific/related kinds of problems, like
-Warray-bounds, or -Wuninitialized.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug tree-optimization/30334] [meta-bug] Request for -Wundefined
[not found] <bug-30334-4@http.gcc.gnu.org/bugzilla/>
2020-04-13 20:27 ` [Bug tree-optimization/30334] [meta-bug] Request for -Wundefined msebor at gcc dot gnu.org
2020-04-13 21:15 ` msebor at gcc dot gnu.org
@ 2020-04-14 6:07 ` egallager at gcc dot gnu.org
2023-05-16 17:40 ` pinskia at gcc dot gnu.org
3 siblings, 0 replies; 4+ messages in thread
From: egallager at gcc dot gnu.org @ 2020-04-14 6:07 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30334
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |egallager at gcc dot gnu.org
--- Comment #18 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Martin Sebor from comment #17)
> I agree with the goal of detecting undefined behavior but I don't think a
> catchall warning option like -Wundefined would be very helpful. Not all
> kinds of undefined behavior are of the same severity so providing a single
> option for all of it would make it hard to clean up code with more than just
> a handful of instances of it. Especially for late warnings that are
> susceptible to false positives, being able to control them in a targeted way
> is important.
>
> The trend over the last years has been toward providing granular warning
> options to control the detection of specific/related kinds of problems, like
> -Warray-bounds, or -Wuninitialized.
and even those could be more granular; for -Warray-bounds clang has a separate
-Warray-bounds-pointer-arithmetic (bug 81172), while for -Wuninitialized, gcc
has a separate -Wmaybe-uninitialized (and, with the static analyzer,
-Wanalyzer-use-of-uninitialized-value), while clang has a separate
-Wsometimes-uninitialized and -Wconditional-uninitialized
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug tree-optimization/30334] [meta-bug] Request for -Wundefined
[not found] <bug-30334-4@http.gcc.gnu.org/bugzilla/>
` (2 preceding siblings ...)
2020-04-14 6:07 ` egallager at gcc dot gnu.org
@ 2023-05-16 17:40 ` pinskia at gcc dot gnu.org
3 siblings, 0 replies; 4+ messages in thread
From: pinskia at gcc dot gnu.org @ 2023-05-16 17:40 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30334
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|gdr at gcc dot gnu.org |unassigned at gcc dot gnu.org
Status|ASSIGNED |NEW
--- Comment #19 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
GDR has not been active in GCC development for years now.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2023-05-16 17:40 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-30334-4@http.gcc.gnu.org/bugzilla/>
2020-04-13 20:27 ` [Bug tree-optimization/30334] [meta-bug] Request for -Wundefined msebor at gcc dot gnu.org
2020-04-13 21:15 ` msebor at gcc dot gnu.org
2020-04-14 6:07 ` egallager at gcc dot gnu.org
2023-05-16 17:40 ` pinskia 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).