On Tue, Sep 15, 2015 at 8:53 AM, Ulrich Weigand <uweig...@de.ibm.com> wrote: > Jim Wilson wrote: > In that case, you might be able to fix the bug by splitting the > offending insns into two patterns, one only handling near mems > and one handling one far mems, where the near/far-ness of the mem > is verified by the *predicate* and not the constraints.
That is how it works currently. He was trying to optimize a case that involved mixed near and far mems and hence couldn't use a predicate in that case. Jim
