[Bug tree-optimization/82689] merging writes of different types to the same location

2021-08-21 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82689

Andrew Pinski  changed:

   What|Removed |Added

   Severity|normal  |enhancement
   Last reconfirmed|2020-03-04 00:00:00 |2021-8-21

[Bug tree-optimization/82689] merging writes of different types to the same location

2020-03-04 Thread msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82689

Martin Sebor  changed:

   What|Removed |Added

   Last reconfirmed|2017-10-24 00:00:00 |2020-3-4
 CC||msebor at gcc dot gnu.org
  Known to fail||10.0, 7.3.0, 8.2.0, 9.1.0

--- Comment #2 from Martin Sebor  ---
Reconfirmed for GCC 10.

[Bug tree-optimization/82689] merging writes of different types to the same location

2017-10-24 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82689

Richard Biener  changed:

   What|Removed |Added

   Keywords||missed-optimization
 Status|UNCONFIRMED |NEW
   Last reconfirmed||2017-10-24
 CC||rguenth at gcc dot gnu.org
 Blocks||33315
 Ever confirmed|0   |1

--- Comment #1 from Richard Biener  ---
We don't currently optimize this (RTL crossjumping does to the extent you are
seeing).  On GIMPLE there's no semantically equivalent code doing an
unconditional store (you'd lose at least some TBAA).

There's a related bug, PR33315, about sinking and commoning stores.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=33315
[Bug 33315] stores not commoned by sinking