[Bug c++/116739] New: template parameter confusion results in parameter packs not expanded with '...'

2024-09-16 Thread ted at lyncon dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116739 Bug ID: 116739 Summary: template parameter confusion results in parameter packs not expanded with '...' Product: gcc Version: unknown Status: UNCONFIRMED Sever

[Bug c++/116714] [14/15 Regression] Inconsistent lambda type inference in function template instance

2024-09-14 Thread ted at lyncon dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116714 --- Comment #6 from Ted Lyngmo --- Darn... :-) Glad you're on it!

[Bug c++/116714] [14/15 Regression] Inconsistent lambda type inference in function template instance

2024-09-14 Thread ted at lyncon dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116714 --- Comment #4 from Ted Lyngmo --- Andrew: The reduced example you provided is not interpreted the same way as what I used when I wrote the report. I think they fail for different reasons. Possibly at different stages. I went through the languag

[Bug c++/116714] New: [14 Regression] Inconsistent lambda type inference in function template instance

2024-09-14 Thread ted at lyncon dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116714 Bug ID: 116714 Summary: [14 Regression] Inconsistent lambda type inference in function template instance Product: gcc Version: 14.0 Status: UNCONFIRMED Severit

[Bug tree-optimization/107087] [12 Regression] bits/stl_algobase.h:431: warning: 'void* __builtin_memcpy(void*, const void*, unsigned int)' reading between 8 and 2147483644 bytes from a region of siz

2024-08-07 Thread ted at lyncon dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107087 Ted Lyngmo changed: What|Removed |Added CC||ted at lyncon dot se --- Comment #20 from

[Bug c++/116051] inconsistent handling of void typedefs in otherwise empty parameter lists

2024-07-23 Thread ted at lyncon dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116051 --- Comment #1 from Ted Lyngmo --- I realized that T in the working usages is non-dependent. I think we can close this right away.

[Bug c++/116051] New: inconsistent handling of void typedefs in otherwise empty parameter lists

2024-07-23 Thread ted at lyncon dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116051 Bug ID: 116051 Summary: inconsistent handling of void typedefs in otherwise empty parameter lists Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: norm

[Bug c++/114625] requires { T{}; } wrongly returns false when T{} is ill-formed while in concept

2024-04-15 Thread ted at lyncon dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114625 --- Comment #5 from Ted Lyngmo --- @Andrew, the title change seems wrong. It wrongly returns true when T{} is ill-formed.

[Bug c++/114625] requires { T{}; } wrongly accepted when T{} is ill-formed while in concept

2024-04-07 Thread ted at lyncon dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114625 Ted Lyngmo changed: What|Removed |Added Summary|requires { T{}; } wrongly |requires { T{}; } wrongly

[Bug c++/114625] New: requires { T{}; } wrongly accepted when T{} is ill-formed

2024-04-07 Thread ted at lyncon dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114625 Bug ID: 114625 Summary: requires { T{}; } wrongly accepted when T{} is ill-formed Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Pri

[Bug c++/114504] New: Non-structural type accepted as non-type template parameter type

2024-03-27 Thread ted at lyncon dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114504 Bug ID: 114504 Summary: Non-structural type accepted as non-type template parameter type Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal

[Bug c++/112349] New: ranges::max makes unecessary copies

2023-11-02 Thread ted at lyncon dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112349 Bug ID: 112349 Summary: ranges::max makes unecessary copies Product: gcc Version: 13.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

[Bug c++/93595] [c++20] function call, substitution failure of template paramter with a lambda default in template context

2023-07-11 Thread ted at lyncon dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93595 --- Comment #8 from Ted Lyngmo --- :-) Ok I tried understanding the Status by reading https://gcc.gnu.org/bugzilla/page.cgi?id=fields.html#bug_status but it doesn't mention NEW. But ok, as long as it's actually a confirmed bug, I'm good.

[Bug c++/93595] [c++20] function call, substitution failure of template paramter with a lambda default in template context

2023-07-11 Thread ted at lyncon dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93595 --- Comment #6 from Ted Lyngmo --- @Andrew Pinski: Shouldn't the status be "CONFIRMED" rather than "NEW"?

[Bug c++/110604] New: template argument deduction failed with decltype(lambda)

2023-07-09 Thread ted at lyncon dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110604 Bug ID: 110604 Summary: template argument deduction failed with decltype(lambda) Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Prio

[Bug c++/108303] New: lookup failes with requires clause on non-template friend function of a class template

2023-01-05 Thread ted at lyncon dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108303 Bug ID: 108303 Summary: lookup failes with requires clause on non-template friend function of a class template Product: gcc Version: 13.0 Status: UNCONFIRMED S

[Bug c++/106110] Expected ambiguity but it resolves fine

2022-06-27 Thread ted at lyncon dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106110 --- Comment #1 from Ted Lyngmo --- Sorry, the helper variable template should be: ``` template static constexpr bool is_foo_call_ambiguous_v = is_foo_call_ambiguous::value; ``` It gives the same result: https://godbolt.org/z/bKbn8Gre7

[Bug c++/106110] New: Expected ambiguity but it resolves fine

2022-06-27 Thread ted at lyncon dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106110 Bug ID: 106110 Summary: Expected ambiguity but it resolves fine Product: gcc Version: 12.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

[Bug c++/105637] [12 Regression] Wrong overload selected in base class

2022-06-03 Thread ted at lyncon dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105637 --- Comment #5 from Ted Lyngmo --- Excellent and thanks!

[Bug c++/105637] New: [11 Regression] Wrong overload selected in base class

2022-05-17 Thread ted at lyncon dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105637 Bug ID: 105637 Summary: [11 Regression] Wrong overload selected in base class Product: gcc Version: 11.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Com

[Bug c++/104565] New: One too many `this`es in parsing?

2022-02-16 Thread ted at lyncon dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104565 Bug ID: 104565 Summary: One too many `this`es in parsing? Product: gcc Version: 10.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++