[Bug c++/100997] [c++20] parse error when id-expression of constructor is simple-template-id

2021-06-09 Thread felix.morgner at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100997 --- Comment #3 from Felix Morgner --- Thank you for the quick response. I will file a bug report with Boost GIL.

[Bug c++/100997] New: [c++20] parse error when id-expression of constructor is simple-template-id

2021-06-09 Thread felix.morgner at gmail dot com via Gcc-bugs
: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: felix.morgner at gmail dot com Target Milestone: --- Created attachment 50972 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50972&action=edit Example source f

[Bug c++/67633] decltype on parenthesized class member access of a prvalue sometimes return wrong results

2017-07-24 Thread felix.morgner at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67633 --- Comment #1 from Felix Morgner --- The same holds true for GCC 7.1 and the deduced type for decltype(auto): #include #include struct s{int v{};}; decltype(auto) f() { return (s{}.v); } int main() { std::cout << std::is_same{} <

[Bug c++/79957] New: [C++] Zero-length array function parameters in templates should cause warning/substituion failure in pedantic mode

2017-03-08 Thread felix.morgner at gmail dot com
: 6.3.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: felix.morgner at gmail dot com Target Milestone: --- According to ISO14882 [dcl.array] zero-length arrays are not

[Bug c++/79832] [C++14/17] result of subscripting non lvalue array should be xvalue

2017-03-03 Thread felix.morgner at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79832 --- Comment #1 from Felix Morgner --- adjusted the title to be more clear. sorry!

[Bug c++/79832] New: [C++14/17] result of array subscript operator should be xvlaue

2017-03-03 Thread felix.morgner at gmail dot com
Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: felix.morgner at gmail dot com Target Milestone: --- According to ISO14882:2014 [expr.sub] (as well as the current draft) the following should yield an xvalue on line 3 (arr{}[0]): int

[Bug c++/78754] New: incorrectly accepts non-deductible template parameter pack in function template

2016-12-09 Thread felix.morgner at gmail dot com
: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: felix.morgner at gmail dot com Target Milestone: --- g++ incorrectly accepts the following code that contains a non-deductible template parameter pack: #include

[Bug libstdc++/78490] [c++17] libstdc++ has undefined behavior in operator= of propagate_const

2016-11-23 Thread felix.morgner at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78490 --- Comment #2 from Felix Morgner --- Comment on attachment 40124 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40124 Proposed patch >--- propagate_const.org2016-11-23 10:28:45.682529129 +0100 >+++ propagate_const.new2016-

[Bug libstdc++/78490] [c++17] libstdc++ has undefined behavior in operator= of propagate_const

2016-11-23 Thread felix.morgner at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78490 --- Comment #1 from Felix Morgner --- Created attachment 40124 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40124&action=edit Proposed patch

[Bug libstdc++/78490] New: [c++17] libstdc++ has undefined behavior in operator= of propagate_const

2016-11-23 Thread felix.morgner at gmail dot com
: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: felix.morgner at gmail dot com Target Milestone: --- The implementation of propagate_const libstdc++ 6.0.22 has undefined behavior in operator= The implementation reads as

[Bug libstdc++/71313] New: [Filesystem TS] remove_all fails to remove directory contents recursively

2016-05-27 Thread felix.morgner at gmail dot com
: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: felix.morgner at gmail dot com Target Milestone: --- Created attachment 38583 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=38583&action=edit Sample

[Bug c++/70979] [C++14] g++ falsely accepts constexpr function returning a lambda

2016-05-06 Thread felix.morgner at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70979 --- Comment #2 from Felix Morgner --- That is why I explicitly referred to C++14. I strongly believe, that the right thing to do would be to disable it (handle it as an error) since it is just that when compiling in C++14 mode. Maybe the error me

[Bug c++/70979] New: [C++14] g++ falsely accepts constexpr function returning a lambda

2016-05-06 Thread felix.morgner at gmail dot com
Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: felix.morgner at gmail dot com Target Milestone: --- Created attachment 38427 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=38427&action=edit The example code g++ acce