On 01/05/2018 01:59 PM, Aldy Hernandez wrote:
> This fixes the code that verifies that none of the uninitialized paths
> reaching a PHI are actually taken (uninit_uses_cannot_happen).
>
> As discussed in the PR, this is done by fixing the predicate analysis in
> tree-ssa-uninit.c so that the set o
Hi,
this patch adds the following builtins in C/C++:
- __builtin_goacc_gang_id
- __builtin_goacc_worker_id
- __builtin_goacc_vector_id
- __builtin_goacc_gang_size
- __builtin_goacc_worker_size
- __builtin_goacc_vector_size
We have openacc C/C++ test-cases using the following nvptx idiom:
...
Hi,
On 05/01/2018 23:46, Michele Pezzutti wrote:
+ __term *= (__k == 0) ? _Tp(1) : -(__mu - (2 * __k - 1) * (2 * __k - 1))
+ / (__k * __8x);
In such cases, per the Coding Standards, you want an outer level of
parentheses wrapping the whole right side expression. See towar
Due to r256284 (PR 78534) there was a latent bug that reared it's head
due to different character length types in the pointer
assignment. Fixed by this patch, which also adds a reduced testcase.
Regtested on x86_64-pc-linux-gnu, committed to trunk as obvious.
gcc/fortran/ChangeLog:
2018-01-06 J
Jeff Law writes:
> On 01/04/2018 02:28 PM, Richard Sandiford wrote:
>> LRA has code to try to prevent cycling, by avoiding reloads that
>> look too similar to the instruction being reloaded. E.g. if we
>> have a R<-C move for some constant C, reloading the source with
>> another R<-C move is unli
On Sat, Jan 06, 2018 at 09:21:59AM +0100, Tom de Vries wrote:
> this patch adds the following builtins in C/C++:
> - __builtin_goacc_gang_id
> - __builtin_goacc_worker_id
> - __builtin_goacc_vector_id
> - __builtin_goacc_gang_size
> - __builtin_goacc_worker_size
> - __builtin_goacc_vector_size
I w
The code in r256209 tried using subregs for two cases: to extract
a lowpart element of a vector, or to extract a subvector from a
wider vector. An earlier version of the SVE port used both variants,
but these days SVE provides vec_extract* for all cases and so only
really needs the subvector extra
Hello world,
the attached patch removes explicit use of dtype in the
array intrinsics, replacing them by macros instead.
Functionally, this patch changes nothing.
The reason is simple: When we change the array descriptor,
for example to implement Fortran 2008 array ranks, to separate
size and ra
On Fri, Jan 05, 2018 at 11:26:59AM +, Richard Sandiford wrote:
> Ping. Here's the patch updated to apply on top of the v8.4 and
> __builtin_load_no_speculate support.
>
> Richard Sandiford writes:
> > This patch switches the AArch64 port to use 2 poly_int coefficients
> > and updates code as
On Fri, Nov 03, 2017 at 05:49:56PM +, Richard Sandiford wrote:
> This patch adds new target selectors for SVE and updates existing
> selectors accordingly. It also XFAILs some tests that don't yet
> work for some SVE modes; most of these go away with follow-on
> vectorisation enhancements.
OK
On Fri, Nov 03, 2017 at 05:50:54PM +, Richard Sandiford wrote:
> This patch adds gcc.target/aarch64 tests for SVE, and forces some
> existing Advanced SIMD tests to use -march=armv8-a.
I'm going to assume that these new testcases are broadly sensible, and not
spend any significant time looking
On Fri, Nov 24, 2017 at 03:59:58PM +, Richard Sandiford wrote:
> Richard Sandiford writes:
> > This series adds support for ARM's Scalable Vector Extension.
> > More details on SVE can be found here:
> >
> >
> > https://developer.arm.com/products/architecture/a-profile/docs/arm-architecture
James Greenhalgh writes:
> On Fri, Jan 05, 2018 at 11:26:59AM +, Richard Sandiford wrote:
>> Ping. Here's the patch updated to apply on top of the v8.4 and
>> __builtin_load_no_speculate support.
>>
>> Richard Sandiford writes:
>> > This patch switches the AArch64 port to use 2 poly_int coe
For printing long characters, we need to use size_t instead of int in
the argument to write_character.
Regtested on x86_64-pc-linux-gnu, approved in the PR, committed to
trunk.
libgfortran/ChangeLog:
2018-01-06 Dominique d'Humieres
Janne Blomqvist
PR fortran/83704
James Greenhalgh writes:
> On Fri, Nov 03, 2017 at 05:50:54PM +, Richard Sandiford wrote:
>> This patch adds gcc.target/aarch64 tests for SVE, and forces some
>> existing Advanced SIMD tests to use -march=armv8-a.
>
> I'm going to assume that these new testcases are broadly sensible, and not
>
On Sat, Jan 6, 2018 at 7:04 PM, Jerry DeLisle wrote:
> Janne,
>
> found this unused warning so need to delete as shown:
>
> diff --git a/libgfortran/io/write.c b/libgfortran/io/write.c
> index c04d243dc08..9639c3092f8 100644
> --- a/libgfortran/io/write.c
> +++ b/libgfortran/io/write.c
> @@ -2372,
James Greenhalgh writes:
> On Fri, Nov 24, 2017 at 03:59:58PM +, Richard Sandiford wrote:
>> Richard Sandiford writes:
>> > This series adds support for ARM's Scalable Vector Extension.
>> > More details on SVE can be found here:
>> >
>> >
>> > https://developer.arm.com/products/architectu
Both a ping and a repost with the new VNx names. See:
https://gcc.gnu.org/ml/gcc-patches/2017-11/msg00592.html
for the full series.
Thanks,
Richard
---
This patch adds support for SVE LD[234], ST[234] and associated
structure modes. Unlike Advanced SIMD, these modes are extra-long
vector
Ping
Richard Sandiford writes:
> This patch adds tests for the SVE structure mode move patterns
> and for LD[234] and ST[234] vectorisation.
>
>
> 2017-11-08 Richard Sandiford
> Alan Hayward
> David Sherwood
>
> gcc/testsuite/
> * gcc.target/aarch64/sve_struct_mov
Bug 83671 - Fix for false positive reported by -Wstringop-overflow
does not work at -O1, points out that the string length range
optimization implemented as a solution for bug 83373 doesn't help
at -O1. The root cause is that the fix was added to the strlen
pass that doesn't run at -O1.
The stri
On 01/06/2018 07:19 AM, Richard Sandiford wrote:
> The code in r256209 tried using subregs for two cases: to extract
> a lowpart element of a vector, or to extract a subvector from a
> wider vector. An earlier version of the SVE port used both variants,
> but these days SVE provides vec_extract* f
On 01/01/2018 03:30 PM, Martin Sebor wrote:
> PR tree-optimization/83640 - ice in generic_overlap at
> gimple-ssa-warn-restrict.c:814 highlights out a class of cases
> where the -Wrestrict checker assumes that the range of a pointer
> offset that us represented by a VR_RANGE has a lower bound that
On 01/06/2018 01:01 AM, Jeff Law wrote:
> On 01/05/2018 01:59 PM, Aldy Hernandez wrote:
>> This fixes the code that verifies that none of the uninitialized paths
>> reaching a PHI are actually taken (uninit_uses_cannot_happen).
>>
>> As discussed in the PR, this is done by fixing the predicate anal
On 5 January 2018 at 00:20, Jeff Law wrote:
> On 01/03/2018 12:08 AM, Prathamesh Kulkarni wrote:
>> On 3 January 2018 at 12:33, Prathamesh Kulkarni
>> wrote:
>>> On 2 January 2018 at 17:49, Jakub Jelinek wrote:
On Tue, Jan 02, 2018 at 05:39:17PM +0530, Prathamesh Kulkarni wrote:
> --- /
As you note in the comments, the code we generate now is actually more
efficient so the test needs to be tweaked.
Rather than checking the form in doloop, I check the form in .combine
and look for
(compare:CC (zero_extend:DI (reg:SI
The test is also twiddled to run on ppc64le.
OK for the trunk
25 matches
Mail list logo
