About three months ago, 4.7 stopped being able to optimise things like:

int *__restrict x = ...;

The (libav) loop microbenchmarks that I'd written used this construct a lot, as an easy way of automatically generating a whole function from a loop kernel.

I spent a while testing 4.7 with the restrict patch reverted, while I caught up with my post-holiday email backlog and saw whether the effect on this code was deliberate. I eventually realised it was, so implemented a change that Ira had suggested: splitting out a peak_loop_1 that takes all the restrict pointers as arguments. I just realised that I never pushed that change back up to bzr, so I've done it now.

Probably a write-only change, since I doubt anyone's going to be using the benchmark again, but just in case :-)

Richard