https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89430
--- Comment #6 from Jiangning Liu <jiangning.liu at amperecomputing dot com> --- (In reply to Richard Biener from comment #5) > (In reply to Jiangning Liu from comment #4) > > > We need to be careful with loads > > > or stores, for instance a load might not trap, while a store would, > > > so if we see a dominating read access this doesn't mean that a later > > > write access would not trap. > > > > Why? For this case, there is a dominating load for the same address. I don't > > see why it might trap. Any example? > > The memory might be mapped readonly. But in such a simple basic block, how can it be mapped readonly? We can easily know it is NOT to do readonly mapping.
