Hi Harald,

sorry, it's on this branch

https://github.com/sourceryinstitute/OpenCoarrays/tree/vehre/issue-779-form-team

only. There is PR for that, but it's not reviewed yet.

- Andre

On Mon, 14 Jul 2025 20:35:32 +0200
Harald Anlauf <anl...@gmx.de> wrote:

> Andre,
> 
> Am 14.07.25 um 18:12 schrieb Andre Vehreschild:
> > Hi Jerry, hi Harald,
> > 
> > I am sorry for not responding earlier. I got a small but urgent project in
> > and have to do it first. It is only three days (w/ continuation possible),
> > but it pays so it has priority.
> > 
> > As for the issues at hand: Jerry, you probably should have the coarray fixes
> > patches from here :
> > https://gcc.gnu.org/pipermail/fortran/2025-July/062470.html on your test
> > branch (both on 15 and 16) to pass the OpenCoarray tests successfully.
> > Because with it: works for me ;-)
> > 
> > Harald, when you look at OpenCoarray's test_teams_1.f90.006.original tree
> > dump (src/tests/unit/teams/ directory), then it may answer your question
> > why I want to put all function evaluation to the calling side and not to
> > the remote accessor. In this testcase w/o my patch the team_number(team)
> > gets moved to the accessor, but `team` can not be moved there (opaque
> > pointer on the source side w/o known size and how to copy).  
> 
> I downloaded OpenCoarrays-2.10.3 but cannot find the file you mention:
> 
> % ls src/tests/unit/teams/
> CMakeLists.txt        teams_coarray_get_by_ref.f90 
> teams_coarray_sendget.f90
> get-communicator.F90  teams_coarray_get.f90          teams_send.f90
> sync-team.f90         teams_coarray_send_by_ref.f90  teams_subset.f90
> team-number.f90       teams_coarray_send.f90
> 
> The only file where grep finds the string test_teams1 is teams_send.f90,
> but I don't see any relation to what you are talking about.
> 
> Can you provide a full path / URL and more details?
> 
> Harald
> 
> > When you test OpenCoarrays, Jerry, then please make sure to use separate and
> > clean build directories. The build stuff from OpenCoarrays is sometimes not
> > cleaning up its artifacts correctly, so that .o's stay that better
> > shouldn't.
> > 
> > Hope to get back to gfortran hacking by mid of the week and that this few
> > tips helped.
> > 
> > Regards,
> >     Andre  
> 
> 


-- 
Andre Vehreschild * Email: vehre ad gmx dot de 

Reply via email to