This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
Perhaps I'm missing something obvious, but often conservative aliasing results in reading lots of extra data from memory. How can speculation compensate for that? It seems that the best you can do is reduce the penalty, if you can do something in parallel with the extra I/O.
You can speculate that a memory location is not changed, and if it is then and only then do you get the extra load?
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |