Hi Richard,
I was trying to have a look at PR35503.
The attached patch tries to warn when an argument is passed to a
restrict-qualified parameter
and the argument could alias with other argument.
For the following test-case:
int f2(int *restrict x, int *y);
void f(void)
{
int a;
f2 (&a, &a);
On Fri, 26 Aug 2016, Prathamesh Kulkarni wrote:
> Hi Richard,
> I was trying to have a look at PR35503.
> The attached patch tries to warn when an argument is passed to a
> restrict-qualified parameter
> and the argument could alias with other argument.
>
> For the following test-case:
> int f2(i
On Thu, Aug 25, 2016 at 9:40 PM, Marc Glisse wrote:
> Hello,
>
> I was considering changing the implementation of _mm_loadu_pd in x86's
> emmintrin.h to avoid a builtin. Here are 3 versions:
>
> typedef double __m128d __attribute__ ((__vector_size__ (16),
> __may_alias__));
> typedef double __m128
On Fri, 26 Aug 2016, Richard Biener wrote:
On Thu, Aug 25, 2016 at 9:40 PM, Marc Glisse wrote:
Hello,
I was considering changing the implementation of _mm_loadu_pd in x86's
emmintrin.h to avoid a builtin. Here are 3 versions:
typedef double __m128d __attribute__ ((__vector_size__ (16),
__may
On Wed, Aug 24, 2016 at 02:47:41AM -0500, Daniel Santos wrote:
> On 08/21/2016 05:59 PM, Segher Boessenkool wrote:
> >On Sun, Aug 21, 2016 at 02:04:49PM -0500, Daniel Santos wrote:
> >>Thanks for the response! Perhaps an UNSPEC insn is needed here because I
> >>have work to do on other passes too.
