Hi Harald,
On 24.08.21 22:36, Harald Anlauf via Fortran wrote:
here's a pretty obvious one: we didn't properly check the arguments
for intrinsics when these had to be ALLOCATABLE and in the case that
argument was a coarray object. Simple solution: just reuse a check
that was used for pointer et
Am 01.09.2021 um 11:02 schrieb Jakub Jelinek:
On Wed, Sep 01, 2021 at 09:06:31AM +0200, Christophe Lyon wrote:
* gfortran.dg/gomp/target-device-ancestor-4.f90: New test.
The last new test fails on aarch64:
/gcc/testsuite/gfortran.dg/gomp/target-device-ancestor-4.f90:7:15: Error:
S
On Thu, Sep 02, 2021 at 02:09:25PM +0200, Marcel Vollweiler wrote:
> gcc/testsuite/ChangeLog:
>
> * gfortran.dg/gomp/target-device-ancestor-4.f90: Comment out dg-final
> to avoid
>UNRESOLVED.
Ok, thanks.
>
> diff --git a/gcc/testsuite/gfortran.dg/gomp/target-device-ancestor-4.f90
Hi Tobias,
> Consider:
>
> type t
>integer, allocatable :: a
> end type t
>
> type(t) :: var[*]
> print *, allocated(var%a)
> print *, allocated(var[1]%a)
> end
what is the problem here? Can you elaborate?
BTW: Intel accepts it, we (currently) accept it, my patch does not change
anything
On 8/18/21 8:57 PM, Sandra Loosemore wrote:
This is a follow-up to commit fef67987cf502fe322e92ddce22eea7ac46b4d75:
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=fef67987cf502fe322e92ddce22eea7ac46b4d75
I realized last week that having multilib-specific versions of
ISO_Fortran_binding.h (g
On 9/2/21 10:18 PM, sunil.k.pandey wrote:
On Linux/x86_64,
93b6b2f614eb692d1d8126ec6cb946984a9d01d7 is the first bad commit
commit 93b6b2f614eb692d1d8126ec6cb946984a9d01d7
Author: Sandra Loosemore
Date: Wed Aug 18 07:22:03 2021 -0700
libgfortran: Further fixes for GFC/CFI descriptor con
