[Bug pch/115312] New: [14/15 Regression] ICE when including a PCH via compiler option -include

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115312 Bug ID: 115312 Summary: [14/15 Regression] ICE when including a PCH via compiler option -include Product: gcc Version: 14.1.0 Status: UNCONFIRMED Severity: nor

[Bug debug/78100] DWARF symbols for an array sometimes missing the array length

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78100 Kevin Puetz changed: What|Removed |Added CC||puetzk at puetzk dot org --- Comment #6 fr

[Bug debug/78100] DWARF symbols for an array sometimes missing the array length

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78100 --- Comment #7 from Kevin Puetz --- Nope, falsified that guess - I just realized compiler explorer can do dwarfdump, which makes it easy to bisect among the releases they have (if not actually commit-by-commit). This shows that 9.5.0 (which has r

[Bug debug/78100] DWARF symbols for an array sometimes missing the array length

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78100 --- Comment #8 from Kevin Puetz --- Found it: this is a duplicate of bug 91507, thus fixed by r276403/31632e2c4327146ea8d21cff33adaa505b17d2bd

[Bug middle-end/32911] Function __attribute__ ((idempotent))

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32911 --- Comment #8 from Eric Gallager --- It might also be worth comparing against the attributes [[unsequenced]] and [[reproducible]] proposed for the C standard: https://www.open-std.org/jtc1/sc22/wg14/www/docs/n2956.htm

[Bug c++/115313] New: False positive -fanalyzer use of uninitialized value due to std::string's default constructor

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115313 Bug ID: 115313 Summary: False positive -fanalyzer use of uninitialized value due to std::string's default constructor Product: gcc Version: 14.1.1 Status: UNCONFIRMED

[Bug analyzer/115313] False positive -fanalyzer use of uninitialized value due to std::string's default constructor

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115313 --- Comment #1 from Jeremy R. --- Reduced: #include std::string foo() { std::string str; return str; } : In function 'std::string foo()': :4:17: warning: use of uninitialized value '' [CWE-457] [-Wanalyzer-use-of-uninitialized-value

[Bug analyzer/115313] False positive -fanalyzer use of uninitialized value due to not understand C++ front-end's NRVO

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115313 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0

[Bug analyzer/111536] -fanalyzer false positive with NRVO return

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111536 Andrew Pinski changed: What|Removed |Added CC||llvm at rifkin dot dev --- Comment #1 f

[Bug analyzer/115313] False positive -fanalyzer use of uninitialized value due to not understand C++ front-end's NRVO

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115313 Andrew Pinski changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW

[Bug analyzer/111536] -fanalyzer false positive with NRVO return

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111536 Andrew Pinski changed: What|Removed |Added Ever confirmed|0 |1 Last reconfirmed|

[Bug c++/115314] New: Type of the `auto` template parameter in a concept is not decayed when called as dependent name

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115314 Bug ID: 115314 Summary: Type of the `auto` template parameter in a concept is not decayed when called as dependent name Product: gcc Version: 15.0 Status: UNCONFIRMED

<    1   2