[Bug middle-end/60102] powerpc fp-bit ices at dwf_regno

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60102 Cesar Philippidis changed: What|Removed |Added CC||cesar at codesourcery dot com

[Bug fortran/63857] New: fixed form OpenACC directive ICE with -fopenacc -fopenmp

Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: cesar at codesourcery dot com Created attachment 33964 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33964&action=edit test case The attached test case causes gfortran to I

[Bug fortran/63858] New: fixed form OpenACC directive ICE with -fopenacc -fopenmp

Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: cesar at codesourcery dot com The attached test case causes gfortran to ICE when -fopenmp is used with -fopenacc. It looks like there is a problem with the way that continuations are handled in

[Bug fortran/63859] New: OpenACC DEVICE_RESIDENT clause

Assignee: unassigned at gcc dot gnu.org Reporter: cesar at codesourcery dot com The OpenACC DEVICE_RESIDENT clause isn't fully supported in gfortran.

[Bug fortran/63861] New: OpenACC coarray ICE

: unassigned at gcc dot gnu.org Reporter: cesar at codesourcery dot com Coarrays in OpenACC accelerated regions causes an ICE in gfortran. The test case gcc/testsuite/gfortran.dg/goacc/coarray.f95 reproduces this failure. It's unclear whether OpenACC 2.0a even supports coarrays. Regar

[Bug fortran/63858] fixed form OpenACC directive ICE with -fopenacc -fopenmp

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63858 --- Comment #2 from Cesar Philippidis --- Created attachment 33967 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33967&action=edit fixed-form ICE

[Bug fortran/63858] fixed form OpenACC directive ICE with -fopenacc -fopenmp

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63858 --- Comment #4 from Cesar Philippidis --- *** Bug 63857 has been marked as a duplicate of this bug. ***

[Bug fortran/63857] fixed form OpenACC directive ICE with -fopenacc -fopenmp

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63857 Cesar Philippidis changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug fortran/63247] New: fortran array alignment in omp target map

: fortran Assignee: unassigned at gcc dot gnu.org Reporter: cesar at codesourcery dot com I've noticed that lower_omp_target is not passing the proper pointer alignment to libgomp for fortran array maps. While this isn't a problem for trunk, it does affect our nvptx target.