[Bug middle-end/96988] Bad/missing warnings when returning a temporary from an inlined function

2021-12-16 Thread msebor at gcc dot gnu.org via Gcc-bugs
||msebor at gcc dot gnu.org Blocks||90556 --- Comment #3 from Martin Sebor --- In the test cases in comment #0 the -Wreturn-local-addr warning is defeated by inlining. By the time the warning sees the program the body of the static

[Bug c/63272] GCC should warn when using pointer to dead scoped variable within the same function

2021-12-16 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63272 Martin Sebor changed: What|Removed |Added CC||oleg.pekar.2017 at gmail dot com ---

[Bug middle-end/98901] missing warning passing a dangling pointer to a function

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

[Bug c/103104] missing warning about superfluous forward declaration -Wsuperfluous-forward-declaration

2021-12-16 Thread msebor at gcc dot gnu.org via Gcc-bugs
||msebor at gcc dot gnu.org Status|UNCONFIRMED |NEW Blocks|87403 | Ever confirmed|0 |1 Severity|normal |enhancement --- Comment #2 from Martin Sebor

[Bug middle-end/101751] asan_test.C fails with excess error with glibc-2.34

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

[Bug c/101604] [meta-bug] bogus/missing -Wvla-parameter

2021-12-16 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101604 Bug 101604 depends on bug 101289, which changed state. Bug 101289 Summary: [11 Regression] bogus -Wvla-paramater warning when using const for vla param https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101289 What|Removed

[Bug c/101289] [11 Regression] bogus -Wvla-paramater warning when using const for vla param

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

[Bug c++/103703] ICE with -Wmismatched-tags with friends and templates

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

[Bug c++/103703] ICE with -Wmismatched-tags with friends and templates

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

[Bug middle-end/102697] [12 Regression] overflow warning missing after -O2 vectorization

2021-12-16 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102697 --- Comment #4 from Martin Sebor --- The warning for the test in comment #0 fails to trigger because of the hack below in pointer-query.cc: /* A helper of compute_objsize_r() to determine the size from MEM_REF MREF. Return true on success

[Bug middle-end/101475] missing -Wstringop-overflow storing a compound literal

2021-12-16 Thread msebor at gcc dot gnu.org via Gcc-bugs
||2021-12-16 Ever confirmed|0 |1 Target Milestone|--- |12.0 Keywords||patch Assignee|unassigned at gcc dot gnu.org |msebor at gcc dot gnu.org --- Comment #2 from Martin

[Bug testsuite/103751] FAIL: gcc.dg/Warray-bounds-48.c (test for excess errors)

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

[Bug testsuite/103751] FAIL: gcc.dg/Warray-bounds-48.c (test for excess errors)

2021-12-16 Thread msebor at gcc dot gnu.org via Gcc-bugs
|testsuite Assignee|unassigned at gcc dot gnu.org |msebor at gcc dot gnu.org --- Comment #2 from Martin Sebor --- The reason for the unexpected warnings is that the test assumes that a struct with just two members, a 32-bit int followed by a 16-bit int, is padded to 64-bits. That a valid

[Bug tree-optimization/88443] [meta-bug] bogus/missing -Wstringop-overflow warnings

2021-12-16 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88443 Bug 88443 depends on bug 102722, which changed state. Bug 102722 Summary: [Disgnostic]Xpass for gcc.dg/Wstringop-overflow-68.c after O2 vectorization. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102722 What|Removed

[Bug middle-end/101475] missing -Wstringop-overflow storing a compound literal

2021-12-16 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101475 Martin Sebor changed: What|Removed |Added CC||crazylht at gmail dot com --- Comment

[Bug middle-end/102722] [Disgnostic]Xpass for gcc.dg/Wstringop-overflow-68.c after O2 vectorization.

2021-12-16 Thread msebor at gcc dot gnu.org via Gcc-bugs
||sparc-sun-solaris2.11 Status|UNCONFIRMED |RESOLVED Last reconfirmed||2021-12-16 CC||msebor at gcc dot gnu.org Host|x86_64-pc-linux-gnu | --- Comment #2

[Bug testsuite/102944] Many gcc.dg/Wstringop-overflow-*.c failures

2021-12-16 Thread msebor at gcc dot gnu.org via Gcc-bugs
||msebor at gcc dot gnu.org Last reconfirmed||2021-12-16 Status|UNCONFIRMED |WAITING --- Comment #5 from Martin Sebor --- I don't see any of the FAILs or XFAILs listed in comment #0 with cross compilers for any of the Targets

[Bug middle-end/103751] New: FAIL: gcc.dg/Warray-bounds-48.c (test for excess errors)

2021-12-16 Thread msebor at gcc dot gnu.org via Gcc-bugs
Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: msebor at gcc dot gnu.org Target Milestone: --- The two tests below show a coupled of failures with the m68k-unknown-linux-gnu cross: Running /src/gcc/master/gcc/testsuite/gcc.dg/dg.exp

[Bug sanitizer/91707] [10/11/12 Regression] spurious stringop-overflow warning with -fsanitize=undefined

2021-12-15 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91707 --- Comment #12 from Martin Sebor --- Here's a slightly simplified test case for GCC 12: $ cat z.c && gcc -O2 -S -Wall -fsanitize=undefined z.c extern void f (unsigned n, long[n], const long[n]); void g (unsigned n, const long a[n]) { long

[Bug sanitizer/91707] [10/11/12 Regression] spurious stringop-overflow warning with -fsanitize=undefined

2021-12-15 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91707 Martin Sebor changed: What|Removed |Added Last reconfirmed|2021-01-21 00:00:00 |2021-12-15 Known to fail|11.0

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

2021-12-15 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||pinskia at gcc dot gnu.org --- Comment

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

2021-12-15 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 Summary|bogus name and location in |[12 Regression] bogus name

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

2021-12-15 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40635 --- Comment #16 from Martin Sebor --- With the patch in comment #13 committed in g:9695e1c23be5b5c55d572ced152897313ddb96ae GCC 12 prints the following for the test case in comment #0: pr40635.c: In function ‘server_init’: pr40635.c:14:9:

[Bug libstdc++/54924] Warn for std::string constructor with wrong size

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

[Bug tree-optimization/90906] diagnose returning pointers to freed memory

2021-12-15 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90906 Martin Sebor changed: What|Removed |Added Keywords||patch --- Comment #3 from Martin Sebor

[Bug tree-optimization/80532] warning on pointer access after free

2021-12-15 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80532 Martin Sebor changed: What|Removed |Added Keywords||patch --- Comment #8 from Martin Sebor

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

2021-12-15 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 85651, which changed state. Bug 85651 Summary: Invalid -Warray-bounds warning with -O3 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85651 What|Removed |Added

[Bug tree-optimization/85651] Invalid -Warray-bounds warning with -O3

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

[Bug other/103736] snprintf bogus format-truncation, disregarding modulo on argument

2021-12-15 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103736 Martin Sebor changed: What|Removed |Added CC||msebor at gcc dot gnu.org --- Comment

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

2021-12-15 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 91457, which changed state. Bug 91457 Summary: FAIL: g++.dg/warn/Warray-bounds-4.C -std=gnu++98 (test for warnings, line 25) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91457 What|Removed

[Bug tree-optimization/91457] FAIL: g++.dg/warn/Warray-bounds-4.C -std=gnu++98 (test for warnings, line 25)

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

[Bug middle-end/98166] bogus -Wmismatched-dealloc on user-defined allocator and inlining

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

[Bug tree-optimization/81592] spurious -Wformat-overflow warning with -fsanitize=signed-integer-overflow

2021-12-15 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81592 Bug 81592 depends on bug 78969, which changed state. Bug 78969 Summary: bogus snprintf truncation warning due to missing range info https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78969 What|Removed |Added

[Bug tree-optimization/78969] bogus snprintf truncation warning due to missing range info

2021-12-15 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78969 Martin Sebor changed: What|Removed |Added Known to fail|8.0 |10.3.0, 11.2.0, 8.3.0,

[Bug c++/103703] ICE with -Wmismatched-tags with friends and templates

2021-12-14 Thread msebor at gcc dot gnu.org via Gcc-bugs
|unassigned at gcc dot gnu.org |msebor at gcc dot gnu.org Keywords||patch Status|NEW |ASSIGNED --- Comment #3 from Martin Sebor --- Patch: https://gcc.gnu.org/pipermail/gcc-patches/2021-December/586856.html

[Bug c++/102036] -Wmismatched-tags doesn't warn for explicit instantations

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

[Bug middle-end/103372] Warning on failure order defaulting to SEQ_CST if not a compile time constant

2021-12-13 Thread msebor at gcc dot gnu.org via Gcc-bugs
||msebor at gcc dot gnu.org --- Comment #4 from Martin Sebor --- The patch for pr99612 submitted last week resolves this problem as well: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99612 Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99612 [Bug 99612] Remove

[Bug middle-end/103483] context-sensitive ranges change triggers stringop-overread

2021-12-10 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103483 --- Comment #13 from Martin Sebor --- The warning for the test case in comment #12 isn't directly related to ranges: it's issued simply because the invalid statement is in the IL and not eliminated by DCE (the secret functions don't let it).

[Bug analyzer/103658] missing -Wanalyzer-use-of-uninitialized-value at -O1 and below for an array access

2021-12-10 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103658 --- Comment #1 from Martin Sebor --- Actually, what I was really after is trying to see if the analyzer would print the conditionals involved in the subscript expressions. But in the simple test case in comment #0 there are no conditionals.

[Bug analyzer/103658] New: missing -Wanalyzer-use-of-uninitialized-value at -O1 and below for an array access

2021-12-10 Thread msebor at gcc dot gnu.org via Gcc-bugs
Severity: normal Priority: P3 Component: analyzer Assignee: dmalcolm at gcc dot gnu.org Reporter: msebor at gcc dot gnu.org Target Milestone: --- I came across this while comparing the middle end -Wuninitialized with -Wanalyzer-use-of-uninitialized-value

[Bug c++/103534] [12 regression] Spurious -Wstringop-overflow warning with std::string concatencation

2021-12-10 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103534 --- Comment #8 from Martin Sebor --- We discussed before (e.g., in PR 93971) the idea of annotating std::string with some attribute telling the optimizer the internal pointer doesn't alias with anything except for the this->_M_local_buf or the

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

2021-12-09 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 103215, which changed state. Bug 103215 Summary: [12 regression] gcc generates unexpected warnings on libx11-1.7.2: error: array subscript -2 is outside array bounds of since r12-3124-g820f0940d7ace130

[Bug tree-optimization/103215] [12 regression] gcc generates unexpected warnings on libx11-1.7.2: error: array subscript -2 is outside array bounds of since r12-3124-g820f0940d7ace130

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

[Bug middle-end/103637] New: [12 Regression] missing warning writing past the end of one of multiple elements of the same array

2021-12-09 Thread msebor at gcc dot gnu.org via Gcc-bugs
: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: msebor at gcc dot gnu.org Target Milestone: --- The fix for pr103215 is too conservative and causes false negatives for past the end accesses

[Bug middle-end/101397] [11 Regression] spurious warning writing to the result of stpcpy minus 1

2021-12-09 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101397 Bug 101397 depends on bug 103143, which changed state. Bug 103143 Summary: [12 Regression] ICE due to infinite recursion in pointer-query.cc https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103143 What|Removed

[Bug middle-end/103143] [12 Regression] ICE due to infinite recursion in pointer-query.cc

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

[Bug tree-optimization/103332] [12 Regression] Spurious -Wstringop-overflow on string concatenation in libstdc++ tests

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

[Bug tree-optimization/96658] Unhelpful -Wstrict-overflow warning from std::push_heap

2021-12-08 Thread msebor at gcc dot gnu.org via Gcc-bugs
||msebor at gcc dot gnu.org Known to fail||10.3.0, 11.2.0, 12.0, 9.3.0 Status|UNCONFIRMED |NEW Last reconfirmed||2021-12-08 --- Comment #1 from Martin Sebor --- Confirmed on trunk plus GCC 9, 10

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

2021-12-08 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 Keywords||patch --- Comment #4 from Martin Sebor

[Bug tree-optimization/103542] [10/11/12 Regregression] bogus -Warray-bounds while index is limited by switch/case

2021-12-04 Thread msebor at gcc dot gnu.org via Gcc-bugs
||56456 CC||msebor at gcc dot gnu.org --- Comment #2 from Martin Sebor --- The IL for the function is below. It seems quite inefficient compared to GCC 9. void get_default_config.part.0 (const uint32_t id) { uint32_t error

[Bug c++/103534] [12 regression] Spurious -Wstringop-overflow warning with std::string concatencation

2021-12-02 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103534 --- Comment #4 from Martin Sebor --- Yes, the warning does disappear when malloc() and free() are used instead of operator new and delete. foo() also ends up much better optimized, even at -O1: __attribute__((abi_tag ("cxx11"))) struct string

[Bug middle-end/103483] context-sensitive ranges change triggers stringop-overread

2021-12-02 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103483 Martin Sebor changed: What|Removed |Added Keywords|missed-optimization | --- Comment #10 from Martin Sebor ---

[Bug tree-optimization/96188] -Wstringop-overflow false positive on std::vector::push_back with -O3

2021-12-02 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96188 Martin Sebor changed: What|Removed |Added Known to work||12.0 --- Comment #9 from Martin Sebor

[Bug tree-optimization/100366] spurious warning - std::vector::clear followed by std::vector::insert(vec.end(), ...) with -O2

2021-12-02 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100366 Martin Sebor changed: What|Removed |Added Known to fail||11.2.0, 12.0 Last

[Bug c++/103534] [12 regression] Spurious -Wstringop-overflow warning with std::string concatencation

2021-12-02 Thread msebor at gcc dot gnu.org via Gcc-bugs
||2021-12-02 Ever confirmed|0 |1 Blocks||88443 CC||msebor at gcc dot gnu.org Status|UNCONFIRMED |NEW --- Comment #1 from Martin Sebor

[Bug tree-optimization/88443] [meta-bug] bogus/missing -Wstringop-overflow warnings

2021-11-30 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88443 Bug 88443 depends on bug 103483, which changed state. Bug 103483 Summary: context-sensitive ranges change triggers stringop-overread https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103483 What|Removed |Added

[Bug middle-end/103483] context-sensitive ranges change triggers stringop-overread

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

[Bug middle-end/103483] context-sensitive ranges change triggers stringop-overread

2021-11-30 Thread msebor at gcc dot gnu.org via Gcc-bugs
||missed-optimization CC||msebor at gcc dot gnu.org --- Comment #3 from Martin Sebor --- The warning is only issued at -O1. It's based on the statement in the IL and the values or ranges of its arguments. In this case the IL

[Bug testsuite/103469] [12 regression] c-c++-common/attr-retain-9.c fails after r12-5483

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

[Bug c++/87403] [Meta-bug] Issues that suggest a new warning

2021-11-23 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87403 Bug 87403 depends on bug 88232, which changed state. Bug 88232 Summary: Please implement -Winfinite-recursion https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88232 What|Removed |Added

[Bug middle-end/88232] Please implement -Winfinite-recursion

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

[Bug c/103360] [meta-bug] bogus/missing -Waddress

2021-11-23 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103360 Bug 103360 depends on bug 96507, which changed state. Bug 96507 Summary: missing -Waddress for member references https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96507 What|Removed |Added

[Bug c++/96507] missing -Waddress for member references

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

[Bug c/79074] -Waddress difference between C and C++ with (T*)0

2021-11-23 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79074 Martin Sebor changed: What|Removed |Added Known to fail||10.2.0, 11.2.0, 12.0,

[Bug c++/96507] missing -Waddress for member references

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

[Bug tree-optimization/103215] [12 regression] gcc generates unexpected warnings on libx11-1.7.2: error: array subscript -2 is outside array bounds of since r12-3124-g820f0940d7ace130

2021-11-22 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103215 Martin Sebor changed: What|Removed |Added Keywords||patch --- Comment #7 from Martin Sebor

[Bug fortran/103369] New: [12 Regression] gfortran.dg/vector_subscript_1.f90

2021-11-22 Thread msebor at gcc dot gnu.org via Gcc-bugs
Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: msebor at gcc dot gnu.org Target Milestone: --- I see the following unexpected failures with today's build of GCC 12: FAIL: gfortran.dg/vector_subscript_1.f90 -O1 execution test FAIL: gfortran.dg

[Bug c++/103363] confusing -Wnonnull-compare testing a reference argument for equality to null

2021-11-22 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103363 Martin Sebor changed: What|Removed |Added Known to fail||10.3.0, 11.2.0, 12.0,

[Bug c++/103363] New: confusing -Wnonnull-compare testing a reference argument for equality to null

2021-11-22 Thread msebor at gcc dot gnu.org via Gcc-bugs
: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: msebor at gcc dot gnu.org Target Milestone: --- Since the conversion of the address of a reference to bool is diagnosed by -Waddress, issuing a second warning for it isn't

[Bug c++/96507] missing -Waddress for member references

2021-11-22 Thread msebor at gcc dot gnu.org via Gcc-bugs
CC| |msebor at gcc dot gnu.org Last reconfirmed||2021-11-22 --- Comment #1 from Martin Sebor --- Confirmed with GCC 12. Since the warning is issued for non-member references (the first case below) but not for members (the second case) I would consider this a

[Bug c/103343] Invalid codegen when comparing pointer to one past the end and then dereferencing that pointer

2021-11-22 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103343 Martin Sebor changed: What|Removed |Added CC||msebor at gcc dot gnu.org --- Comment

[Bug c/103360] [meta-bug] bogus/missing -Waddress

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

[Bug c/103360] New: [meta-bug] bogus/missing -Waddress

2021-11-22 Thread msebor at gcc dot gnu.org via Gcc-bugs
Assignee: unassigned at gcc dot gnu.org Reporter: msebor at gcc dot gnu.org Target Milestone: --- This is a meta-bug to track false positives and negatives in the -Waddress warning first introduced in GCC 4.2 (in r122136).

[Bug c/78989] Missing -Waddress warning due to -Wno-system-headers

2021-11-22 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78989 --- Comment #9 from Martin Sebor --- GCC 12 (and prior, down to 10) warns for the test case: $ cat pr78989.ii && gcc -S -Wall pr78989.ii int asan_poison_variables () { return (asan_poison_variables && # 6 "gimplify.cpp" 3 4

[Bug c/102867] [12 Regression] -Waddress from macro expansion in readelf.c

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

[Bug c++/33925] [10/11 Regression] gcc -Waddress lost some useful warnings

2021-11-19 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=33925 Martin Sebor changed: What|Removed |Added Known to work||12.0 Summary|[10/11/12

[Bug c/103334] New: missing -Wc++-compat for a function redeclared with different qualifiers

2021-11-19 Thread msebor at gcc dot gnu.org via Gcc-bugs
: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: msebor at gcc dot gnu.org Target Milestone: --- Redeclaring a function that differs only in the qualifiers on the return type is rejected by G++ in all C++ modes but not diagnosed

[Bug tree-optimization/103332] Spurious -Wstringop-overflow warnings in libstdc++ tests

2021-11-19 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103332 Martin Sebor changed: What|Removed |Added CC||msebor at gcc dot gnu.org See

[Bug c/103310] null comparison with a weak symbol eliminated

2021-11-17 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103310 Martin Sebor changed: What|Removed |Added Component|middle-end |c --- Comment #1 from Martin Sebor ---

[Bug middle-end/98503] [11/12 regression] -Warray-bounds false positive with global variables at -O2 since r11-3306-g3f9a497d1b0dd9da

2021-11-17 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98503 Martin Sebor changed: What|Removed |Added CC||slyfox at gcc dot gnu.org --- Comment

[Bug middle-end/103292] [12 regression] xorg-server-1.20.13 -Werror=array-bounds false positive on unions

2021-11-17 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103292 Martin Sebor changed: What|Removed |Added Resolution|INVALID |DUPLICATE Component|c

[Bug tree-optimization/102759] [12 Regression] ICE: Segmentation fault in maybe_check_access_sizes since r12-2976-gb48d4e6818674898

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

[Bug middle-end/103310] New: null comparison with a weak symbol eliminated

2021-11-17 Thread msebor at gcc dot gnu.org via Gcc-bugs
: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: msebor at gcc dot gnu.org Target Milestone: --- The following test case was prompted by the discussion in the review of a -Waddress enhancement: https://gcc.gnu.org/pipermail/gcc-patches/2021-November/584749.html

[Bug c/101702] [12 Regression] ICE: in handle_argspec_attribute, at c-family/c-attribs.c:3623

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

[Bug c/103292] [12 regression] xorg-server-1.20.13 -Werror=array-bounds false positive on unions

2021-11-16 Thread msebor at gcc dot gnu.org via Gcc-bugs
|--- |INVALID Keywords||diagnostic See Also||https://gcc.gnu.org/bugzill ||a/show_bug.cgi?id=102151 CC||msebor at gcc

[Bug c/101702] [12 Regression] ICE: in handle_argspec_attribute, at c-family/c-attribs.c:3623

2021-11-16 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101702 --- Comment #5 from Martin Sebor --- (In reply to Jakub Jelinek from comment #4) > Martin clearly prefers some other fix, so I'll let him fix it himself. I think I just misread your change. It doesn't cause the problem I was concerned about.

[Bug tree-optimization/102960] [10/11 Regression] ICE: in sign_mask, at wide-int.h:855 in GCC 10.3.0

2021-11-16 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102960 Martin Sebor changed: What|Removed |Added Known to fail|12.0| Known to work|

[Bug tree-optimization/103223] [12 regression] Access attribute dropped when ipa-sra is applied

2021-11-15 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103223 --- Comment #9 from Martin Sebor --- Outside of code comments only the user-visible attribute access interface is documented in the manual. The main difference is probably that attribute access can be added by the user for any pair of

[Bug tree-optimization/103176] -foptimize-strlen causes stringop-overflow warning

2021-11-15 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103176 --- Comment #7 from Martin Sebor --- You're welcome and no need to apologize. We want to improve the warnings (and the rest of the compiler) and these reports help us understand both the limitations and opportunities for improvements, or at

[Bug tree-optimization/102759] [12 Regression] ICE: Segmentation fault in maybe_check_access_sizes since r12-2976-gb48d4e6818674898

2021-11-15 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102759 Martin Sebor changed: What|Removed |Added Keywords||patch --- Comment #4 from Martin Sebor

[Bug tree-optimization/103223] [12 regression] Access attribute dropped when ipa-sra is applied

2021-11-15 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103223 --- Comment #7 from Martin Sebor --- For an attribute access that's explicitly specified on the declaration of a function I think these steps should work: 1) Call init_attr_rdwr_indices() to initialize the mapping for the original function

[Bug tree-optimization/103215] [12 regression] gcc generates unexpected warnings on libx11-1.7.2: error: array subscript -2 is outside array bounds of since r12-3124-g820f0940d7ace130

2021-11-15 Thread msebor at gcc dot gnu.org via Gcc-bugs
at gcc dot gnu.org |msebor at gcc dot gnu.org

[Bug tree-optimization/103215] [12 regression] gcc generates unexpected warnings on libx11-1.7.2: error: array subscript -2 is outside array bounds of since r12-3124-g820f0940d7ace130

2021-11-15 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103215 Martin Sebor changed: What|Removed |Added Blocks||56456 --- Comment #6 from Martin Sebor

[Bug c/101702] [12 Regression] ICE: in handle_argspec_attribute, at c-family/c-attribs.c:3623

2021-11-15 Thread msebor at gcc dot gnu.org via Gcc-bugs
at gcc dot gnu.org |msebor at gcc dot gnu.org

[Bug tree-optimization/102009] [12 Regression] ICE: in gimple_call_arg, at gimple.h:3272 by r12-2976

2021-11-15 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102009 --- Comment #3 from Martin Sebor --- gimple_builtin_call_types_compatible_p() returns false even for calls with trivial mismatches like an int where a size_t is expected. I would prefer a less restrictive test that doesn't prevent detecting

[Bug tree-optimization/103223] [12 regression] Access attribute dropped when ipa-sra is applied

2021-11-15 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103223 --- Comment #5 from Martin Sebor --- (In reply to Martin Jambor from comment #4) > (In reply to Jan Hubicka from comment #0) ... > > Martin, I wonder if if you would be OK with simply dropping the access when > > function signature changes

[Bug tree-optimization/88443] [meta-bug] bogus/missing -Wstringop-overflow warnings

2021-11-12 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88443 Bug 88443 depends on bug 103176, which changed state. Bug 103176 Summary: -foptimize-strlen causes stringop-overflow warning https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103176 What|Removed |Added

[Bug tree-optimization/103176] -foptimize-strlen causes stringop-overflow warning

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

[Bug middle-end/97048] [meta-bug] bogus/missing -Wstringop-overread warnings

2021-11-12 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97048 Bug 97048 depends on bug 98465, which changed state. Bug 98465 Summary: Bogus -Wstringop-overread with -std=gnu++20 -O2 and std::string::insert https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98465 What|Removed

[Bug middle-end/98465] Bogus -Wstringop-overread with -std=gnu++20 -O2 and std::string::insert

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

<    1   2   3   4   5   6   7   8   9   10   >