Displaying 2 results from an estimated 2 matches for "second_call".
2016 Mar 16
3
the as-if rule / perf vs. security
...-bit loads. I think it is
> semantically very similar to this situation as well...
>
> v4i32 first_call(int *x) { //use all of the array
> int f0 = x[0];
> int f1 = x[1];
> int f2 = x[2];
> int f3 = x[3];
> return (v4i32) { f0, f1, f2, f3 };
> }
> v4i32 second_call(int *x) { //use some of the array
> int s0 = x[0];
> int s1 = x[1];
> int s2 = 0;
> int s3 = x[3];
> return (v4i32) { s0, s1, s2, s3 };
> }
> first_call(x);
> second_call(x);
>
> The implementation isn't going to zero out the stack in between those
&...
2016 Mar 16
3
the as-if rule / perf vs. security
Hi Ben -
Thanks for your response. For the sake of argument, let's narrow the scope
of the problem to eliminate some of the variables you have rightfully
cited.
Let's assume we're not dealing with volatiles, atomics, or FP operands.
We'll even guarantee that the extra loaded value is never used. This is, in
fact, the scenario that http://reviews.llvm.org/rL263446 is concerned