https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68738
Rian Quinn changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68738
--- Comment #4 from Rian Quinn ---
To expand on this issue, any attempt to use the following pattern will result
in instability:
some_type *p = &var;
*p or p-> // Crash
A couple of situations that I have seen include:
- allocate memory in g
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68738
--- Comment #3 from Rian Quinn ---
Just for completeness, here is the exact code out objdump output:
class Blah1
{
public:
Blah1() {}
virtual ~Blah1() {}
virtual int foo() { return 0; }
};
class Blah2 : public Blah1
{
public:
B
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68738
--- Comment #2 from Rian Quinn ---
Yeah I'm am pretty sure it is specific to TARGET=elf-x86_64 (i.e. no OS
specified). When I ran the same test on Ubuntu's native GCC it ran fine.
objdump showed pretty different assembly for the Ubuntu case,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68738
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
--- Comment
