You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Testing out the new polymorphic assignment feature, I can trigger lots of segfaults in the fortran runtime. I am reporting these as separate failures even though they clearly could be related. Search for #polysegfaults .
Compiling the below code with flang (no additional options) produces a binary that gives a runtime segfault assigning to y from the output of the spread intrinsic.
program test
implicit none
type t
integer i
end type
class(t),allocatable :: x(:)
class(t),allocatable :: y(:,:)
allocate(t::x(2))
y = spread(x,dim=1,ncopies=1)
select type(y)
type is (t)
print *,y(1,1)
end select
end program
This has very similar backtrace to #831 with a very large size being malloced by the runtime.
Tested with eab3991 built with llvm9 branches of both llvm and flang-driver on AArch64
The text was updated successfully, but these errors were encountered:
Testing out the new polymorphic assignment feature, I can trigger lots of segfaults in the fortran runtime. I am reporting these as separate failures even though they clearly could be related. Search for #polysegfaults .
Compiling the below code with flang (no additional options) produces a binary that gives a runtime segfault assigning to
y
from the output of thespread
intrinsic.This has very similar backtrace to #831 with a very large size being malloced by the runtime.
Tested with eab3991 built with llvm9 branches of both llvm and flang-driver on AArch64
The text was updated successfully, but these errors were encountered: