https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104615
Bug ID: 104615
Summary: [Concepts] ICE in explicit instantiation when multiple
candidates are valid (CWG2421)
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Se
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105174
Bug ID: 105174
Summary: [Concepts] Example from temp.func.order-p6 selects
wrong overload
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81501
--- Comment #9 from Roy Jacobson ---
Thanks for the patch! I wonder if it would handle coroutines correctly. Clang
has this open bug https://github.com/llvm/llvm-project/issues/47179 that is
related to this optimization.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107085
Bug ID: 107085
Summary: __reference_constructs_from_temporary does not detect
static up-cast
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107085
--- Comment #3 from Roy Jacobson ---
Thanks! But a Base const& is still not detected:
static_assert(__reference_constructs_from_temporary(Base const&, Derived));
And in this case I think it _is_ a bug that this doesn't compile?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107513
Bug ID: 107513
Summary: [Feature Request] Implement
__attribute__((__nodebug__))
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
P
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107513
--- Comment #2 from Roy Jacobson ---
I might be using it wrong? But it doesn't seem to do anything:
https://godbolt.org/z/9bdKhz4E7
It would be nice to at least avoid having the function's name in the binary,
clang does it with nodebug.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107513
--- Comment #5 from Roy Jacobson ---
I still think it might be good idea to introduce this for the sake of reducing
debug symbols size. I'm less interested in improving debug experience in this
case, but obviously any improvement to that is welc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105699
Bug ID: 105699
Summary: [Concepts] Constrained virtual functions are accepted
by GCC
Product: gcc
Version: 12.1.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105699
--- Comment #1 from Roy Jacobson ---
I want to suggest to also consider the case of overloading virtual functions
with non-virtual constrained functions. There's an open CWG issue about this
https://www.open-std.org/jtc1/sc22/wg21/docs/cwg_activ
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106085
Bug ID: 106085
Summary: It's unclear what the __has_trivial* builtins do after
P0848 (Conditionally Trivial Special Member Functions)
Product: gcc
Version: unknown
Statu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81501
Roy Jacobson changed:
What|Removed |Added
CC||roi.jacobson1 at gmail dot com
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109941
Bug ID: 109941
Summary: [feat req] Add an option to mark STL types as
nodiscard
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Pr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109941
--- Comment #2 from Roy Jacobson ---
Right, libc++ do that as well since 2019 -
https://reviews.llvm.org/D65900?id=213975.
Although with the RAII classes I think you need to [[nodiscard]] the
constructor which I think (?) is a compiler extensio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109941
--- Comment #4 from Roy Jacobson ---
The linked bug is about nodiscard applied to the class together with ignoring
temporary objects. But GCC will when the type is the return value or when the
nodiscard is applied to the constructor:
class [[no
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108588
Bug ID: 108588
Summary: __is_constructible returns wrong value for invalid
(but non deleted) default constructor
Product: gcc
Version: unknown
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108769
Bug ID: 108769
Summary: [C++20] __is_trivial returns true even if a default
constructor's constrains are unsatisfied
Product: gcc
Version: unknown
Status: UNCONFIRMED
17 matches
Mail list logo