https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110814
Bug ID: 110814
Summary: Address Sanitizer misses 'global-buffer-overflow' for
const arrays
Product: gcc
Version: 13.1.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110099
Bug ID: 110099
Summary: GCC's Address Sanitizer misses 'stack-use-after-scope'
when accessing variable from the same scope
Product: gcc
Version: unknown
Status: UNCONFIR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109923
Bug ID: 109923
Summary: Template friend function defined in a template class
becomes a friend of all instantiations, not one
Product: gcc
Version: unknown
Status: UNCONF
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108565
Bug ID: 108565
Summary: -Wuse-after-free false positive on a shared_ptr
implementation triggered by -O2
Product: gcc
Version: unknown
Status: UNCONFIRMED
Sever
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105729
Bug ID: 105729
Summary: False positive UBsan "reference binding to null
pointer of type" when evaluating array indexing which
throws exception
Product: gcc
Versi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103362
--- Comment #2 from Egor Suvorov ---
Thank you very much, sent a report there:
https://sourceware.org/bugzilla/show_bug.cgi?id=28619
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103362
Bug ID: 103362
Summary: -m option is not ignored when is immediately preceded
by -o option
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98677
--- Comment #4 from Egor Suvorov ---
Note that the issue requires both UBSanitizer and Valgrind enabled
simultaneously. Running with just one of them does not result in an error.
The versions are ones installed in Ubuntu 20.04.3 Focal Fossa (amd
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100764
--- Comment #1 from Egor Suvorov ---
UPD: compiling with `g++ -v -std=c++20` on Godbolt's GCC 11.1 yields the
following information about versions:
Using built-in specs.
COLLECT_GCC=/opt/compiler-explorer/gcc-11.1.0/bin/g++
Target: x86_64-linux
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100764
Bug ID: 100764
Summary: Internal compiler error when unable to deduce template
parameter value
Product: gcc
Version: 11.1.0
Status: UNCONFIRMED
Severity: norma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99931
Bug ID: 99931
Summary: Unnamed `struct` defined with `using` having internal
linkage instead of external, unlike `typedef`,
yielding different semantics for two
Product: gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96188
--- Comment #5 from Egor Suvorov ---
Created attachment 50214
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50214&action=edit
Preprocessor output for Egor Suvorov's example
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96188
Egor Suvorov changed:
What|Removed |Added
CC||egor_suvorov at mail dot ru
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98677
Bug ID: 98677
Summary: std::regex constructor triggers valgrind under clang++
with undefined sanitizer; possible use-after-move
Product: gcc
Version: unknown
Status: UNCO
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98019
--- Comment #1 from Egor Suvorov ---
Also, I would expect a warning in this case:
requires {
foo(); // Looks like a statement.
};
but not this:
requires {
static_cast(foo());
};
or this:
requires {
{ foo() }; // expression chec
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98019
Bug ID: 98019
Summary: Concepts: compound requirement expression from
'requires' expression is considered discarded-value
expression for [[nodiscard]], false positive warning
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97755
Bug ID: 97755
Summary: Explicit default constructor is called during
copy-list-initialization with a warning only
Product: gcc
Version: 10.2.0
Status: UNCONFIRMED
17 matches
Mail list logo
