[llvm-commits] [PATCH] Remove readonly/readnone attributes from all called functions

[Evgeniy Stepanov]

  > I can't imagine such situation. readonly/readnone is an optimistic information. If we don't have it, we simply can't do something.

  What I mean is this function had these attribute for some time - it was born readonly, and side effects were added later. While it was still readonly, some optimization could have happened.

  I'm pretty sure this is not an issue for MemorySanitizer, because our side effects are limited to out private globals, and it's really hard to imagine an optimization that could be broken by this.

http://llvm-reviews.chandlerc.com/D173