https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110186
--- Comment #3 from Amir Ansari ---
Sorry, it is warning about C::C() = default rather than B::B() = default;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110186
--- Comment #2 from Amir Ansari ---
The compiler is warning about B::B() = default. That is C++ 11. How can you say
it has not been updated for C++11?
Meyer's updated book has a slightly different name:
Effective Modern C++: 42 Specific Ways t
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: amir.ahmed.ansari at outlook dot com
Target Milestone: ---
Created attachment 55293
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55293&action=edit
Code to replicate the problem
Compile the attach
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: amir.ahmed.ansari at outlook dot com
Target Milestone: ---
Created attachment 55292
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55292&action=edit
Code to replicate the problem
Compile the attach
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: amir.ahmed.ansari at outlook dot com
Target Milestone: ---
The following code:
template
struct C
{
void f()
{
(
[&, this]()
{
}.oper
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: amir.ahmed.ansari at outlook dot com
Target Milestone: ---
Created attachment 49219
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49219&action=edit
Failing program
The a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94132
--- Comment #2 from Amir Ansari ---
(In reply to Andrew Pinski from comment #1)
> >Can we make this check more robust so valid usage isn't rejected?
>
> Why do you think it is valid?
Because I know the flexible array member data isn't dangling
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: amir.ahmed.ansari at outlook dot com
Target Milestone: ---
Until gcc 9.2.0, the following usage was correct:
struct S {
int size;
int data[];
};
struct {
S s;
int data[16];
} var
