[Bug libstdc++/78713] [missed optimization] gcc doesn't use clobbers to optimize constructors

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78713 Marc Glisse changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill

[Bug libstdc++/78713] [missed optimization] gcc doesn't use clobbers to optimize constructors

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78713 --- Comment #4 from Avi Kivity --- This bug has a cousin https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61982 where the optimizer doesn't eliminate a store to an object that is about to be destroyed. While for sure it

[Bug libstdc++/78713] [missed optimization] gcc doesn't use clobbers to optimize constructors

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78713 --- Comment #3 from Richard Biener --- Currently the middle-end only knows about constructors via DECL_CXX_CONSTRUCTOR_P. I suppose it would be more useful to communicate that a function fully initializes an object pointed to by parameter X.

[Bug libstdc++/78713] [missed optimization] gcc doesn't use clobbers to optimize constructors

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78713 --- Comment #2 from Avi Kivity --- I think the middle-end knows it is safe to write to *this, because this is happening in a constructor, so all of the object's memory is known clobbered. Similarly, if the assignment

[Bug libstdc++/78713] [missed optimization] gcc doesn't use clobbers to optimize constructors

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78713 Richard Biener changed: What|Removed |Added Keywords||missed-optimization