Ira Rosen writes:
>> This test fails on spu-elf, and presumably all other targets that
>> don't have mmap (or ) ...
>>
>> Can the test be restricted to those targets that actually support
>> that OS feature?
>
> I copied the list of targets from gcc.dg/20050826-1.c.
Sorry, but this is a bad idea
On Sun, Jul 17, 2011 at 7:57 AM, Ira Rosen wrote:
> On 15 July 2011 15:56, Ulrich Weigand wrote:
>> Ira Rosen wrote:
>>
>>> * gcc.dg/vect/pr49038.c: New test.
>>
>>> Index: testsuite/gcc.dg/vect/pr49038.c
>>> ===
>>> --- testsu
On 15 July 2011 15:56, Ulrich Weigand wrote:
> Ira Rosen wrote:
>
>> * gcc.dg/vect/pr49038.c: New test.
>
>> Index: testsuite/gcc.dg/vect/pr49038.c
>> ===
>> --- testsuite/gcc.dg/vect/pr49038.c (revision 0)
>> +++ testsuite/gc
Ira Rosen wrote:
> * gcc.dg/vect/pr49038.c: New test.
> Index: testsuite/gcc.dg/vect/pr49038.c
> ===
> --- testsuite/gcc.dg/vect/pr49038.c (revision 0)
> +++ testsuite/gcc.dg/vect/pr49038.c (revision 0)
> @@ -0,0 +1,38 @@
>
On Thu, Jun 2, 2011 at 6:06 PM, Ira Rosen wrote:
> On 26 May 2011 10:52, Ira Rosen wrote:
>> Hi,
>>
>> The vectorizer supports strided loads with gaps, e.g., when only a[4i]
>> and a[4i+2] are accessed, it generates a vector load a[4i:4i+3], i.e.,
>> creating an access to a[4i+3], which doesn't e
On 26 May 2011 10:52, Ira Rosen wrote:
> Hi,
>
> The vectorizer supports strided loads with gaps, e.g., when only a[4i]
> and a[4i+2] are accessed, it generates a vector load a[4i:4i+3], i.e.,
> creating an access to a[4i+3], which doesn't exist in the scalar code.
> This access maybe invalid as d
On Thu, May 26, 2011 at 12:52 AM, Ira Rosen wrote:
> Hi,
>
> The vectorizer supports strided loads with gaps, e.g., when only a[4i]
> and a[4i+2] are accessed, it generates a vector load a[4i:4i+3], i.e.,
> creating an access to a[4i+3], which doesn't exist in the scalar code.
> This access maybe
Hi,
The vectorizer supports strided loads with gaps, e.g., when only a[4i]
and a[4i+2] are accessed, it generates a vector load a[4i:4i+3], i.e.,
creating an access to a[4i+3], which doesn't exist in the scalar code.
This access maybe invalid as described in the PR.
This patch creates an epilogue
