https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96306
Tobias Burnus changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96306
Richard Biener changed:
What|Removed |Added
Target Milestone|11.2|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96306
--- Comment #13 from CVS Commits ---
The master branch has been updated by Julian Brown :
https://gcc.gnu.org/g:c0f8c22a3e9f8cd45c1cb4be5f83afbebe3bfdc9
commit r12-1911-gc0f8c22a3e9f8cd45c1cb4be5f83afbebe3bfdc9
Author: Julian Brown
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96306
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|11.0|11.2
--- Comment #12 from Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96306
Thomas Schwinge changed:
What|Removed |Added
Target Milestone|--- |11.0
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96306
--- Comment #10 from CVS Commits ---
The master branch has been updated by Tobias Burnus :
https://gcc.gnu.org/g:2e764ae1d666002b136726e6548481013527197d
commit r11-2328-g2e764ae1d666002b136726e6548481013527197d
Author: Tobias Burnus
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96306
--- Comment #9 from Tobias Burnus ---
Initial TI support for AMDGCN has been committed, see:
https://gcc.gnu.org/pipermail/gcc-patches/2020-July/550663.html
https://gcc.gnu.org/g:8d0b2b33748014ee57973c1d7bc9fd7706bb3da9
commit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96306
--- Comment #8 from Andrew Stubbs ---
I'm loath to enable TImode if it's going to ICE all over the place, and I can't
just drop everything else and implement working TImode unless there's an easy
solution. It's always been on the nice-to-have
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96306
--- Comment #7 from Tobias Burnus ---
At least as in-between solution, one could change libgfortran to disable
HAVE_GFC_INTEGER_16 for gcn. — libgfortran exercises a lot of the integer
arithmetics, which we do not need here.
One just needs to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96306
--- Comment #6 from Jakub Jelinek ---
Only by slowing down all 64-bit targets in OpenMP for Fortran by using the
indirection (and make it incompatible with C/C++ too, which is even worse).
I wasn't aware that gcn is BITS_PER_WORD 32 target, that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96306
--- Comment #5 from Andrew Stubbs ---
GCC will automatically generate libgcc calls for types up to 2*BITS_PER_WORD,
but no further. Since BITS_PER_WORD is 32 on GCN this means no automatic TImode
support for anything that would go that route
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96306
--- Comment #4 from Jakub Jelinek ---
Most targets don't have 128-bit GPR instructions, either none at all, or most
of them. That doesn't mean it isn't easy to support it, for the simpler
operations like basic arithmetics, if there is no optab
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96306
--- Comment #3 from Andrew Stubbs ---
TImode was added for use by a few instructions that take two 64-bit values in
consecutive registers. It's also useful for the SLP fake vectorization stuff.
It wasn't intended for use with user types; I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96306
--- Comment #2 from Tobias Burnus ---
Just as background: While OpenMP uses for C/C++ a typedef for 'omp_depend_t',
which maps to a struct with "char[2*sizeof(*void)]", for Fortran an integer
kind is required by the OpenMP spec.
At least with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96306
--- Comment #1 from Jakub Jelinek ---
Unlike non-offloading targets where there is always an option to just use
smaller omp_depend_kind and instead treat it as pointer to malloced struct and
free at the end, like done on some targets for locks,
15 matches
Mail list logo
