https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64181
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64181
Andrew Pinski changed:
What|Removed |Added
Known to work||8.4.0
--- Comment #7 from Andrew Pinski
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64181
Andrew Pinski changed:
What|Removed |Added
Known to work||9.1.0
--- Comment #6 from Andrew Pinski
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64181
--- Comment #5 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #4)
> Seems to be fixed in GCC 10+. It looks like GCC is handling volatile more
> correctly now.
Note I could only get the original testcase to show the issue not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64181
Andrew Pinski changed:
What|Removed |Added
Known to work||10.0
--- Comment #4 from Andrew Pinski
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64181
--- Comment #3 from Mikhail Maltsev miyuki at gcc dot gnu.org ---
A sligtly modified testcase (no templates, no lambdas, inconsistent behavior in
single invocation).
struct Raiser
{
virtual void raise() __attribute__((noinline))
{
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64181
Mikhail Maltsev miyuki at gcc dot gnu.org changed:
What|Removed |Added
Keywords||wrong-code
