[Bug c/99295] [9/10/11 Regression] documentation on __attribute__((malloc)) is wrong

2021-03-01 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99295 Martin Sebor changed: What|Removed |Added Known to fail||10.2.1, 9.3.0 Summary|[11 Regr

[Bug c/99276] grammar in diagnostics for overflowing the destination

2021-03-01 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99276 Martin Sebor changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug c/99276] grammar in diagnostics for overflowing the destination

2021-03-01 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99276 Martin Sebor changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |msebor at gcc dot gnu.org

[Bug c/99317] Missed warning

2021-03-02 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99317 Martin Sebor changed: What|Removed |Added CC||msebor at gcc dot gnu.org Resolut

[Bug c++/99251] [11 Regression] inconsistent -Wnonnull warning behaviour with dynamic_cast

2021-03-02 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99251 Martin Sebor changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[Bug middle-end/95507] [meta-bug] bogus/missing -Wnonnull

2021-03-02 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95507 Bug 95507 depends on bug 99251, which changed state. Bug 99251 Summary: [11 Regression] inconsistent -Wnonnull warning behaviour with dynamic_cast https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99251 What|Removed

[Bug c/99295] [9/10 Regression] documentation on __attribute__((malloc)) is wrong

2021-03-02 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99295 Martin Sebor changed: What|Removed |Added Known to fail|11.0| Summary|[9/10/11 Regression]

[Bug middle-end/99276] grammar in diagnostics for overflowing the destination

2021-03-02 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99276 Martin Sebor changed: What|Removed |Added Component|c |middle-end Status|ASSIGNED

[Bug translation/40883] [meta-bug] Translation breakage with trivial fixes

2021-03-02 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40883 Bug 40883 depends on bug 99276, which changed state. Bug 99276 Summary: grammar in diagnostics for overflowing the destination https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99276 What|Removed |Added -

[Bug middle-end/99367] New: missing warning on constructing/destroying class objects in insufficient space

2021-03-03 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99367 Bug ID: 99367 Summary: missing warning on constructing/destroying class objects in insufficient space Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: n

[Bug middle-end/99370] New: calling a virtual function in insufficient space silently folded to __builtin_unreachable

2021-03-03 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99370 Bug ID: 99370 Summary: calling a virtual function in insufficient space silently folded to __builtin_unreachable Product: gcc Version: 11.0 Status: UNCONFIRMED

[Bug c/99420] New warning -Warray-parameter

2021-03-08 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99420 --- Comment #3 from Martin Sebor --- The false positive is caused by the local redeclaration of f1() in h() below not having had the type attributes added to it describing the form of the array. This happens because instead of merging the type a

[Bug sanitizer/99418] sanitizer checks for accessing multidimentional VLA-array

2021-03-08 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99418 Martin Sebor changed: What|Removed |Added CC||msebor at gcc dot gnu.org --- Comment #5

[Bug tree-optimization/99473] New: redundant conditional zero-initialization not eliminated

2021-03-08 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99473 Bug ID: 99473 Summary: redundant conditional zero-initialization not eliminated Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priori

[Bug tree-optimization/97631] [10 Regression] bogus "writing one too many bytes" warning for memcpy with strlen argument

2021-03-08 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97631 Martin Sebor changed: What|Removed |Added Known to fail|11.0| Summary|[10/11 Regression] bo

[Bug middle-end/98266] [11 Regression] bogus array subscript is partly outside array bounds on virtual inheritance

2021-03-08 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98266 Martin Sebor changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[Bug tree-optimization/56456] [meta-bug] bogus/missing -Warray-bounds

2021-03-08 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56456 Bug 56456 depends on bug 98266, which changed state. Bug 98266 Summary: [11 Regression] bogus array subscript is partly outside array bounds on virtual inheritance https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98266 What|Removed

[Bug tree-optimization/99474] New: missing warning on an out of bounds VLA access by a pointer

2021-03-08 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99474 Bug ID: 99474 Summary: missing warning on an out of bounds VLA access by a pointer Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Pri

[Bug tree-optimization/99475] New: [10/11 Regression] bogus -Warray-bounds accessing an array element of empty structs

2021-03-08 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99475 Bug ID: 99475 Summary: [10/11 Regression] bogus -Warray-bounds accessing an array element of empty structs Product: gcc Version: 11.0 Status: UNCONFIRMED Severi

[Bug tree-optimization/99475] [10/11 Regression] bogus -Warray-bounds accessing an array element of empty structs

2021-03-08 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99475 Martin Sebor changed: What|Removed |Added Known to fail||10.2.0, 11.0 Status|UNCONFIRM

[Bug tree-optimization/99475] [10/11 Regression] bogus -Warray-bounds accessing an array element of empty structs

2021-03-08 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99475 Martin Sebor changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |msebor at gcc dot gnu.org

[Bug sanitizer/99418] more cases where -fsanitize=bounds can check one-past-the-end accesses

2021-03-09 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99418 Martin Sebor changed: What|Removed |Added Blocks||56456 Status|WAITING

[Bug tree-optimization/99489] [11 Regression] internal compiler error: during GIMPLE pass: strlen in dlt_logstorage_log_file_name()

2021-03-09 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99489 Martin Sebor changed: What|Removed |Added CC||msebor at gcc dot gnu.org Last reconfir

[Bug tree-optimization/99489] [11 Regression] internal compiler error: during GIMPLE pass: strlen in dlt_logstorage_log_file_name()

2021-03-09 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99489 Martin Sebor changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill

[Bug tree-optimization/82429] strcpy to stpcpy transformation disabled in strict mode

2021-03-09 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82429 Martin Sebor changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED

[Bug tree-optimization/99489] [11 Regression] internal compiler error: during GIMPLE pass: strlen in dlt_logstorage_log_file_name()

2021-03-09 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99489 Martin Sebor changed: What|Removed |Added Blocks||88781 Keywords|

[Bug tree-optimization/99502] New: missing -Warray-bounds on partial out of bounds access in C++

2021-03-09 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99502 Bug ID: 99502 Summary: missing -Warray-bounds on partial out of bounds access in C++ Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal P

[Bug tree-optimization/99502] missing -Warray-bounds on partial out of bounds access in C++

2021-03-09 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99502 Martin Sebor changed: What|Removed |Added Last reconfirmed||2021-03-10 Keywords|

[Bug middle-end/99525] New: wrong location of implicitly generated assignment to polymorphic class

2021-03-10 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99525 Bug ID: 99525 Summary: wrong location of implicitly generated assignment to polymorphic class Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal

[Bug middle-end/99525] wrong location of implicitly generated assignment to polymorphic class

2021-03-10 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99525 --- Comment #1 from Martin Sebor --- The (otherwise untested) change below corrects the location: diff --git a/gcc/tree-inline.c b/gcc/tree-inline.c index 1dcb31c0267..c77745b788d 100644 --- a/gcc/tree-inline.c +++ b/gcc/tree-inline.c @@ -4938,7

[Bug tree-optimization/99532] New: missing warning on placement new into smaller space

2021-03-10 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99532 Bug ID: 99532 Summary: missing warning on placement new into smaller space Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component

[Bug c/99578] gcc-11 -Warray-bounds or -Wstringop-overread warning when accessing a pointer from integer literal

2021-03-13 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99578 Martin Sebor changed: What|Removed |Added CC||msebor at gcc dot gnu.org --- Comment #1

[Bug tree-optimization/99489] [11 Regression] internal compiler error: during GIMPLE pass: strlen in dlt_logstorage_log_file_name()

2021-03-13 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99489 Martin Sebor changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[Bug middle-end/88781] [meta-bug] bogus/missing -Wstringop-truncation warnings

2021-03-13 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88781 Bug 88781 depends on bug 99489, which changed state. Bug 99489 Summary: [11 Regression] internal compiler error: during GIMPLE pass: strlen in dlt_logstorage_log_file_name() https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99489 What|

[Bug tree-optimization/99580] False positive -Warray-bounds with -O2

2021-03-13 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99580 Martin Sebor changed: What|Removed |Added Keywords||diagnostic Ever confirmed|0

[Bug middle-end/99578] gcc-11 -Warray-bounds or -Wstringop-overread warning when accessing a pointer from integer literal

2021-03-13 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99578 Martin Sebor changed: What|Removed |Added Component|c |middle-end Keywords|

[Bug middle-end/99578] gcc-11 -Warray-bounds or -Wstringop-overread warning when accessing a pointer from integer literal

2021-03-15 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99578 --- Comment #8 from Martin Sebor --- (In reply to Arnd Bergmann from comment #6) > I figured out the qnx4 warning in the end: https://godbolt.org/z/hvqjr3 The false positive is a known problem caused by redundancy elimination (the FRE/PRE passes

[Bug middle-end/99578] gcc-11 -Warray-bounds or -Wstringop-overread warning when accessing a pointer from integer literal

2021-03-15 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99578 --- Comment #9 from Martin Sebor --- (In reply to Richard Biener from comment #7) > Note heuristically 0xe8ffc000 isn't likely such an offset from a NULL > pointer object because the object would be quite large. > > The diagnostic could maybe al

[Bug middle-end/99612] Remove "#pragma GCC system_header" from atomic file to warn on incorrect memory order

2021-03-16 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99612 Martin Sebor changed: What|Removed |Added Last reconfirmed||2021-03-16 Target Milestone|---

[Bug middle-end/99612] Remove "#pragma GCC system_header" from atomic file to warn on incorrect memory order

2021-03-16 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99612 Martin Sebor changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|unassigned at

[Bug middle-end/99612] Remove "#pragma GCC system_header" from atomic file to warn on incorrect memory order

2021-03-16 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99612 --- Comment #3 from Martin Sebor --- The test case: $ (set -x && cat pr99612.C && g++ -O2 -S -Wall --std=c++20 -O2 -Wall -Winvalid-memory-model pr99612.C && g++ -O2 -S -Wall --std=c++20 -O2 -Wall -Winvalid-memory-model -Wsystem-headers pr99612.C

[Bug middle-end/99630] New: missing -Warray-bounds accessing a trailing array of a virtual base class

2021-03-17 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99630 Bug ID: 99630 Summary: missing -Warray-bounds accessing a trailing array of a virtual base class Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal

[Bug middle-end/99630] missing -Warray-bounds accessing a trailing array of a virtual base class

2021-03-17 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99630 --- Comment #1 from Martin Sebor --- It might be worth warning for any out of bounds access to trailing members of polymorphic classes, regardless of whether the type of the complete enclosing object is known (and known to be derived virtually).

[Bug tree-optimization/99632] New: missing warning accessing a trailing zero length array member of base class

2021-03-17 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99632 Bug ID: 99632 Summary: missing warning accessing a trailing zero length array member of base class Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: norm

[Bug tree-optimization/99632] missing warning accessing a trailing zero length array member of base class

2021-03-17 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99632 --- Comment #2 from Martin Sebor --- The definition missing from comment #0 is: struct B { int n, a[0]; };

[Bug tree-optimization/99635] New: -Warray-bounds where -Wzero-length-bounds is expected

2021-03-17 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99635 Bug ID: 99635 Summary: -Warray-bounds where -Wzero-length-bounds is expected Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Compone

[Bug c++/99642] Compiler error while using precompiled header and -Wmismatched-tags flag

2021-03-18 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99642 Martin Sebor changed: What|Removed |Added Keywords||ice-on-valid-code Status|UNCO

[Bug c++/99642] Compiler error while using precompiled header and -Wmismatched-tags flag

2021-03-18 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99642 Martin Sebor changed: What|Removed |Added Known to fail||10.2.0, 11.0 --- Comment #2 from Martin S

[Bug tree-optimization/99502] missing -Warray-bounds on partial out of bounds access in C++

2021-03-18 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99502 Martin Sebor changed: What|Removed |Added Status|ASSIGNED|RESOLVED Target Milestone|---

[Bug c++/99642] Compiler error while using precompiled header and -Wmismatched-tags flag

2021-03-18 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99642 --- Comment #3 from Martin Sebor --- Type and spec are the messages facet, but the same problem happens with other types. A simpler test case is: $ (set -x && cat pch.h && cat main.cpp) + cat pch.h #include + cat main.cpp #include #include "p

[Bug sanitizer/99673] [11 Regression] bogus -Wstringop-overread warning with address sanitizer due to member address substitution

2021-03-19 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99673 Martin Sebor changed: What|Removed |Added Known to fail||11.0 Status|UNCONFIRMED

[Bug middle-end/99676] New: missing detail in warning for passing smaller array to bigger argument

2021-03-19 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99676 Bug ID: 99676 Summary: missing detail in warning for passing smaller array to bigger argument Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: minor

[Bug middle-end/99676] missing detail in warning for passing smaller array to bigger argument

2021-03-19 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99676 Martin Sebor changed: What|Removed |Added Keywords||diagnostic Blocks|

[Bug sanitizer/99673] [11 Regression] bogus -Wstringop-overread warning with address sanitizer due to member address substitution

2021-03-21 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99673 --- Comment #3 from Martin Sebor --- None of the -Wstringop-xxx warnings (either true or false positives) affects code generation. Thanks for the true vs false positive breakdown. If you remember and could let me know the details of the real bu

[Bug middle-end/99714] New: warn about alloca/dealloc mismatches based on calls with same object in different functions

2021-03-22 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99714 Bug ID: 99714 Summary: warn about alloca/dealloc mismatches based on calls with same object in different functions Product: gcc Version: 11.0 Status: UNCONFIRMED

[Bug middle-end/99715] New: bogus/missing Wmismatched-dealloc warnings

2021-03-22 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99715 Bug ID: 99715 Summary: bogus/missing Wmismatched-dealloc warnings Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-

[Bug middle-end/99714] warn about alloca/dealloc mismatches based on calls with same object in different functions

2021-03-22 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99714 Martin Sebor changed: What|Removed |Added Keywords||documentation Blocks|

[Bug middle-end/99715] [meta-bug] bogus/missing Wmismatched-dealloc warnings

2021-03-22 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99715 Martin Sebor changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED

[Bug middle-end/99714] warn about alloca/dealloc mismatches based on calls with same object in different functions

2021-03-23 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99714 Martin Sebor changed: What|Removed |Added Assignee|dmalcolm at gcc dot gnu.org|unassigned at gcc dot gnu.org

[Bug tree-optimization/99739] New: [11 Regression] missing optimization of a repeated conditional

2021-03-23 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99739 Bug ID: 99739 Summary: [11 Regression] missing optimization of a repeated conditional Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal

[Bug tree-optimization/99755] New: failure to fold a conditional that's a subset of another expression

2021-03-24 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99755 Bug ID: 99755 Summary: failure to fold a conditional that's a subset of another expression Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal

[Bug tree-optimization/99756] New: bogus -Wmaybe-uninitialized with a use conditional that's a subset of a defining conditional

2021-03-24 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99756 Bug ID: 99756 Summary: bogus -Wmaybe-uninitialized with a use conditional that's a subset of a defining conditional Product: gcc Version: 11.0 Status: UNCONFIRMED

[Bug tree-optimization/99756] bogus -Wmaybe-uninitialized with a use conditional that's a subset of a defining conditional

2021-03-24 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99756 Martin Sebor changed: What|Removed |Added Keywords||diagnostic Depends on|

[Bug middle-end/99768] [11 Regression] Bogus -Wuninitialized diagnostic with type punning

2021-03-25 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99768 Martin Sebor changed: What|Removed |Added Last reconfirmed||2021-03-25 Status|UNCONFIRMED

[Bug tree-optimization/33802] bogus "is used uninitialized" (VOPs) (inlining)

2021-03-25 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=33802 Martin Sebor changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug middle-end/24639] [meta-bug] bug to track all Wuninitialized issues

2021-03-25 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24639 Bug 24639 depends on bug 33802, which changed state. Bug 33802 Summary: bogus "is used uninitialized" (VOPs) (inlining) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=33802 What|Removed |Added

[Bug fortran/31279] Uninitialized warning for call-by-reference arguments with known intent(in)

2021-03-25 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31279 Martin Sebor changed: What|Removed |Added Component|middle-end |fortran --- Comment #7 from Martin Sebor

[Bug middle-end/36823] missing uninitialized warning (IPA, inlining)

2021-03-25 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36823 --- Comment #5 from Martin Sebor --- Bisection shows the -Wuninitialized at -O2 disappeared between r176911 and r176920. The likely candidate is r176918.

[Bug tree-optimization/40635] bogus name and location in 'may be used uninitialized' warning

2021-03-25 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40635 Martin Sebor changed: What|Removed |Added Last reconfirmed|2019-02-24 00:00:00 |2021-3-25 Known to fail|9.0

[Bug tree-optimization/40635] bogus name and location in 'may be used uninitialized' warning

2021-03-25 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40635 Martin Sebor changed: What|Removed |Added Target Milestone|--- |12.0 Status|NEW

[Bug middle-end/24639] [meta-bug] bug to track all Wuninitialized issues

2021-03-25 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24639 Bug 24639 depends on bug 44547, which changed state. Bug 44547 Summary: -Wuninitialized reports false warning in nested switch statements (missed switch optimization) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44547 What|Removed

[Bug tree-optimization/44547] -Wuninitialized reports false warning in nested switch statements (missed switch optimization)

2021-03-25 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44547 Martin Sebor changed: What|Removed |Added Resolution|--- |FIXED CC|

[Bug tree-optimization/48483] Construct from yourself w/o warning

2021-03-25 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48483 Martin Sebor changed: What|Removed |Added Known to work||10.2.0, 11.0, 5.1.0 Status|NE

[Bug c++/52167] self-initialization should at least produce use-of-uninitialized warning

2021-03-25 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52167 Bug 52167 depends on bug 48483, which changed state. Bug 48483 Summary: Construct from yourself w/o warning https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48483 What|Removed |Added

[Bug tree-optimization/52167] self-initialization should at least produce use-of-uninitialized warning

2021-03-25 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52167 Martin Sebor changed: What|Removed |Added Resolution|--- |FIXED Known to fail|

[Bug middle-end/24639] [meta-bug] bug to track all Wuninitialized issues

2021-03-25 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24639 Bug 24639 depends on bug 52167, which changed state. Bug 52167 Summary: self-initialization should at least produce use-of-uninitialized warning https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52167 What|Removed |

[Bug tree-optimization/52523] Missing "uninitialized" warning (VOP, taking address of var)

2021-03-25 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52523 Martin Sebor changed: What|Removed |Added CC||msebor at gcc dot gnu.org Sta

[Bug middle-end/24639] [meta-bug] bug to track all Wuninitialized issues

2021-03-25 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24639 Bug 24639 depends on bug 52523, which changed state. Bug 52523 Summary: Missing "uninitialized" warning (VOP, taking address of var) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52523 What|Removed |Added ---

[Bug tree-optimization/40635] bogus name and location in 'may be used uninitialized' warning

2021-03-25 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40635 Martin Sebor changed: What|Removed |Added CC||pa...@matos-sorge.com --- Comment #15 fro

[Bug middle-end/53917] Wuninitialized warning points to place where variable doesn't occur

2021-03-25 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53917 Martin Sebor changed: What|Removed |Added Resolution|--- |DUPLICATE CC|

[Bug middle-end/24639] [meta-bug] bug to track all Wuninitialized issues

2021-03-25 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24639 Bug 24639 depends on bug 53917, which changed state. Bug 53917 Summary: Wuninitialized warning points to place where variable doesn't occur https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53917 What|Removed |Added

[Bug tree-optimization/83336] [meta-bug] Issues with displaying inlining chain for middle-end warnings

2021-03-25 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83336 Bug 83336 depends on bug 53917, which changed state. Bug 53917 Summary: Wuninitialized warning points to place where variable doesn't occur https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53917 What|Removed |Added

[Bug middle-end/24639] [meta-bug] bug to track all Wuninitialized issues

2021-03-25 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24639 Bug 24639 depends on bug 54804, which changed state. Bug 54804 Summary: -Wuninitialized fails to warn about uninitialized local union https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54804 What|Removed |Added --

[Bug middle-end/54804] -Wuninitialized fails to warn about uninitialized local union

2021-03-25 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54804 Martin Sebor changed: What|Removed |Added Resolution|--- |FIXED CC|

[Bug tree-optimization/55060] False un-initialized variable warnings (fixed, add testcase to testsuite)

2021-03-25 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55060 Martin Sebor changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug middle-end/24639] [meta-bug] bug to track all Wuninitialized issues

2021-03-25 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24639 Bug 24639 depends on bug 55060, which changed state. Bug 55060 Summary: False un-initialized variable warnings (fixed, add testcase to testsuite) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55060 What|Removed

[Bug tree-optimization/55288] Improve handling/suppression of maybe-uninitialized warnings

2021-03-25 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55288 Martin Sebor changed: What|Removed |Added Target Milestone|--- |4.9.0 CC|

gcc-bugs@gcc.gnu.org

2021-03-26 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56574 Martin Sebor changed: What|Removed |Added Keywords||missed-optimization Known to fail|

[Bug tree-optimization/56654] uninit warning behaves erratically (always executed block, "is" vs "may", order when walking uses)

2021-03-26 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56654 Martin Sebor changed: What|Removed |Added Keywords||diagnostic Last reconfirmed|2014-09-12

[Bug fortran/56670] Allocatable-length character var causes bogus warning with -Wuninitialized

2021-03-26 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56670 Martin Sebor changed: What|Removed |Added Known to fail||10.2.0, 11.0, 4.8.4, 4.9.4,

[Bug middle-end/57832] compiling sha-256 code (xz 5.0.5) generates false warnings when using -march=native on Atom CPU

2021-03-26 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57832 Martin Sebor changed: What|Removed |Added Last reconfirmed|2018-10-09 00:00:00 |2021-3-26 Known to fail|

[Bug tree-optimization/59970] Bogus Wuninitialized warnings at low optimization levels

2021-03-26 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59970 Martin Sebor changed: What|Removed |Added Target Milestone|--- |7.0 CC|

[Bug middle-end/24639] [meta-bug] bug to track all Wuninitialized issues

2021-03-26 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24639 Bug 24639 depends on bug 59970, which changed state. Bug 59970 Summary: Bogus Wuninitialized warnings at low optimization levels https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59970 What|Removed |Added ---

[Bug middle-end/60488] missing uninitialized warning (address taken, VOP)

2021-03-26 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60488 Martin Sebor changed: What|Removed |Added Last reconfirmed|2016-08-23 00:00:00 |2021-3-26 Known to fail|7.0

[Bug middle-end/57832] compiling sha-256 code (xz 5.0.5) generates false warnings when using -march=native on Atom CPU

2021-03-27 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57832 --- Comment #6 from Martin Sebor --- In the reduced test cases (in comment #3 and comment #4) d is a global variable so it's value is zero. c is assigned in the first iteration of the loop (when e is zero) and used in subsequent iterations when

[Bug tree-optimization/43361] missing uninitialized warning without optimization (-O0) (PHI in always_executed basic block)

2021-03-29 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43361 Martin Sebor changed: What|Removed |Added Last reconfirmed|2010-03-14 15:45:50 |2021-3-29 --- Comment #14 from Martin Seb

[Bug middle-end/60488] missing uninitialized warning (address taken, VOP)

2021-03-29 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60488 --- Comment #8 from Martin Sebor --- You're right, the test cases aren't equivalent, or meant to be. What I want to highlight is that in the test case in comment #6, in g() and other similar ones like it the warning is most likely going to be a

[Bug middle-end/61112] Simple example triggers false-positive -Wmaybe-uninitialized warning

2021-03-29 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61112 Martin Sebor changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill

[Bug middle-end/61428] wrong "maybe-uninitialized" (jump threading? predicate analysis?)

2021-03-29 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61428 Martin Sebor changed: What|Removed |Added Resolution|--- |FIXED Target Milestone|---

[Bug tree-optimization/19794] [meta-bug] Jump threading related bugs

2021-03-29 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19794 Bug 19794 depends on bug 61428, which changed state. Bug 61428 Summary: wrong "maybe-uninitialized" (jump threading? predicate analysis?) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61428 What|Removed |Added -

  1   2   3   4   5   6   7   8   9   10   >