[Bug libstdc++/115480] New: Difference between trivial copyability of std::pair under Clang in C++23

2024-06-13 Thread ldionne.2 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115480 Bug ID: 115480 Summary: Difference between trivial copyability of std::pair under Clang in C++23 Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: norma

[Bug c++/111419] New: Eager instantiation of function return type in concept causes compilation error

2023-09-14 Thread ldionne.2 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111419 Bug ID: 111419 Summary: Eager instantiation of function return type in concept causes compilation error Product: gcc Version: 14.0 Status: UNCONFIRMED Severity

[Bug c++/103511] __builtin_bit_cast requires a constructor call

2023-07-07 Thread ldionne.2 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103511 --- Comment #5 from Louis Dionne --- Note that my claim about TriviallyCopyable is taken from the Standard here, for reference (even though Jason probably knows this by heart :-). https://eel.is/c++draft/class.prop#1: > A trivially copyable cl

[Bug c++/103511] __builtin_bit_cast requires a constructor call

2023-07-07 Thread ldionne.2 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103511 Louis Dionne changed: What|Removed |Added CC||ldionne.2 at gmail dot com --- Comment #

[Bug c++/110000] GCC should implement exclude_from_explicit_instantiation

2023-06-01 Thread ldionne.2 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=11 --- Comment #13 from Louis Dionne --- Nikolas already answered some, but just to expand on this: > But on the topic of this enhancement request, I don't see why functions > should be excluded from explicit instantiation if they're already abi-

[Bug c++/110000] GCC should implement exclude_from_explicit_instantiation

2023-05-31 Thread ldionne.2 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=11 --- Comment #9 from Louis Dionne --- (In reply to Andrew Pinski from comment #3) > I am getting a feeling this attribute is well defined enough. > > Is it really just supposed to block explicit instantiation of templates? > Is there a decent se

[Bug c++/110000] GCC should implement exclude_from_explicit_instantiation

2023-05-26 Thread ldionne.2 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=11 Louis Dionne changed: What|Removed |Added CC||ldionne.2 at gmail dot com --- Comment #

[Bug bootstrap/107795] recursion through breaks non-GNU implementations of the C++ stdlib

2022-11-21 Thread ldionne.2 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107795 --- Comment #13 from Louis Dionne --- Let me rephrase my whole request here. I understand that what GCC does work for GCC and GCC-adjacent projects. This report is about making the behavior of more friendly to implementations that are not GCC-

[Bug bootstrap/107795] recursion through breaks non-GNU implementations of the C++ stdlib

2022-11-21 Thread ldionne.2 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107795 --- Comment #11 from Louis Dionne --- (In reply to Andrew Pinski from comment #9) > > GCC version specific includes > GCC version specific fixincludes > C library > includes > > That is for C. > C++ is: > libstdc++ library includes > ... (rest

[Bug bootstrap/107795] recursion through breaks non-GNU implementations of the C++ stdlib

2022-11-21 Thread ldionne.2 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107795 --- Comment #8 from Louis Dionne --- (In reply to Andrew Pinski from comment #5) > (In reply to Louis Dionne from comment #4) > > (In reply to Andrew Pinski from comment #2) > > > You should not be building on top of GCC's limits.h header at all

[Bug bootstrap/107795] recursion through breaks non-GNU implementations of the C++ stdlib

2022-11-21 Thread ldionne.2 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107795 --- Comment #4 from Louis Dionne --- (In reply to Andrew Pinski from comment #2) > You should not be building on top of GCC's limits.h header at all really. > Rather implementations should have their own. What do you mean by "implementations"?

[Bug libstdc++/107795] New: recursion through breaks non-GNU implementations of the C++ stdlib

2022-11-21 Thread ldionne.2 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107795 Bug ID: 107795 Summary: recursion through breaks non-GNU implementations of the C++ stdlib Product: gcc Version: 12.1.0 Status: UNCONFIRMED Severity: normal

[Bug libstdc++/48101] obscure error message with std::set

2022-03-10 Thread ldionne.2 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48101 Louis Dionne changed: What|Removed |Added CC||ldionne.2 at gmail dot com --- Comment #1

[Bug c++/104760] Attribute [[deprecated]] causes diagnostic in never-instantiated template

2022-03-02 Thread ldionne.2 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104760 --- Comment #3 from Louis Dionne --- (In reply to Marek Polacek from comment #2) > And I think this is the same problem as in > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=33911#c18. Not sure if we want > to change anything. Yup, I agree this

[Bug c++/33911] attribute deprecated vs. templates

2022-03-02 Thread ldionne.2 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=33911 Louis Dionne changed: What|Removed |Added CC||ldionne.2 at gmail dot com --- Comment #2

[Bug c++/104760] New: Attribute [[deprecated]] causes diagnostic in never-instantiated template

2022-03-02 Thread ldionne.2 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104760 Bug ID: 104760 Summary: Attribute [[deprecated]] causes diagnostic in never-instantiated template Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: norm

[Bug c++/70816] bogus error __builtin_strcmp is not a constant expression in a constexpr function

2021-12-15 Thread ldionne.2 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70816 Louis Dionne changed: What|Removed |Added CC||ldionne.2 at gmail dot com --- Comment #3

[Bug c++/102247] New: Overload resolution with brace-init is ambiguous when it shouldn't be

2021-09-08 Thread ldionne.2 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102247 Bug ID: 102247 Summary: Overload resolution with brace-init is ambiguous when it shouldn't be Product: gcc Version: unknown Status: UNCONFIRMED Severity: norma

[Bug c++/97675] GCC does not allow turning off the warning for exceptions being caught by an earlier handler

2020-11-06 Thread ldionne.2 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97675 --- Comment #3 from Louis Dionne --- Thanks a lot!

[Bug c++/97675] New: GCC does not allow turning off the warning for exceptions being caught by an earlier handler

2020-11-02 Thread ldionne.2 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97675 Bug ID: 97675 Summary: GCC does not allow turning off the warning for exceptions being caught by an earlier handler Product: gcc Version: 11.0 Status: UNCONFIRMED