Dear all,
this patch addresses overeager optimization of Cray pointers when
used in comparisons. Cray pointers are non-standard, and odd in a
sense that they were introduced before modern Fortran pointers.
Comparisons with e.g. a "NULL" pointer are actually comparisons
with integer zero etc., whi
On 1/2/25 12:04 PM, Harald Anlauf wrote:
Dear all,
this patch addresses overeager optimization of Cray pointers when
used in comparisons. Cray pointers are non-standard, and odd in a
sense that they were introduced before modern Fortran pointers.
Comparisons with e.g. a "NULL" pointer are actua
On Tue, 31 Dec 2024, Sandra Loosemore wrote:
> diff --git a/gcc/fortran/intrinsic.texi b/gcc/fortran/intrinsic.texi
> index d11d37761d9..b47180126ca 100644
> --- a/gcc/fortran/intrinsic.texi
> +++ b/gcc/fortran/intrinsic.texi
> @@ -1577,7 +1577,7 @@ if @var{Y} is present, @var{X} shall be REAL.
>
On 1/2/25 20:22, Maciej W. Rozycki wrote:
On Tue, 31 Dec 2024, Sandra Loosemore wrote:
diff --git a/gcc/fortran/intrinsic.texi b/gcc/fortran/intrinsic.texi
index d11d37761d9..b47180126ca 100644
--- a/gcc/fortran/intrinsic.texi
+++ b/gcc/fortran/intrinsic.texi
@@ -1577,7 +1577,7 @@ if @var{Y} is
Support the 'has_device_addr' clause with OpenMP's 'dispatch'
directive.
The testcase is even more questionable as the C/C++ testcase
(looking at it globally/semantically), but it tests (locally)
what it is supposed to test: namely, 'has_device_addr' does not
fulfill the 'is_device_ptr' property
