https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63157
--- Comment #2 from haynberg at sig dot com ---
I recently read your old PR about placement new -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=29286.
Is using placement new also a means to prevent strict-aliasing optimizations
here? I don’t
ormal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: haynberg at sig dot com
Basically, I want to build with strict aliasing enabled however I'd like a way
to *programmatically* prevent strict aliasing optimizations if needed.
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: haynberg at sig dot com
I'm not sure if this is a bug or allowed by the standard. Either way, it's
strange this is allowed.
$ cat t.cpp
#include
using namespace std;
struct X {
void foo();
};
// an unlimi
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: haynberg at sig dot com
The last two lines of output should be the same ("has iterator") but, for some
reason, GCC requires the member function to be qualified for the non-variadic
