[Bug fortran/87326] [F18] Support the NEW_INDEX= specifier in the FORM TEAM statement

[Bug fortran/87326] [F18] Support the NEW_INDEX= specifier in the FORM TEAM statement

[everythingfunctional at protonmail dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87326

Brad Richardson <everythingfunctional at protonmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |everythingfunctional@proton
                   |                            |mail.com

--- Comment #3 from Brad Richardson <everythingfunctional at protonmail dot com> ---
Was there any more progress on this? I've just run into it.

FYI I'm trying implement a polymorphic send/receive:
https://gitlab.com/everythingfunctional/communicator

[Bug fortran/87326] [F18] Support the NEW_INDEX= specifier in the FORM TEAM statement

[kargl at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87326

kargl at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kargl at gcc dot gnu.org

--- Comment #4 from kargl at gcc dot gnu.org ---
(In reply to Brad Richardson from comment #3)
> Was there any more progress on this? I've just run into it.
> 
> FYI I'm trying implement a polymorphic send/receive:
> https://gitlab.com/everythingfunctional/communicator

Unfortunately, no.  gfortran depends on opencoarray for its library support for
coarray Fortran.  Much of the work has been contributed by individuals funded
through the Sourcery Institute (i.e., Damian's organization).  He's turned his
interests towards caffeine (https://github.com/berkeleylab/caffeine).

[Bug fortran/87326] [F18] Support the NEW_INDEX= specifier in the FORM TEAM statement

[weeks at iastate dot edu]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87326

--- Comment #5 from Nathan Weeks <weeks at iastate dot edu> ---
(In reply to Brad Richardson from comment #3)
> Was there any more progress on this? I've just run into it.
> 
> FYI I'm trying implement a polymorphic send/receive:
> https://gitlab.com/everythingfunctional/communicator

The FSF copyright assignment ended up being an unexpectedly-difficult hurdle at
the time. I could try again if there is interest, though it would also require
some effort to rework the original patch for GCC 14. If another contributor
were willing to submit a clean-room implementation, that may be more expedient.

[Bug fortran/87326] [F18] Support the NEW_INDEX= specifier in the FORM TEAM statement

[anlauf at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87326

--- Comment #6 from anlauf at gcc dot gnu.org ---
(In reply to Nathan Weeks from comment #5)
> (In reply to Brad Richardson from comment #3)
> > Was there any more progress on this? I've just run into it.
> > 
> > FYI I'm trying implement a polymorphic send/receive:
> > https://gitlab.com/everythingfunctional/communicator
> 
> The FSF copyright assignment ended up being an unexpectedly-difficult hurdle
> at the time. I could try again if there is interest, though it would also
> require some effort to rework the original patch for GCC 14. If another
> contributor were willing to submit a clean-room implementation, that may be
> more expedient.

Besides the copyright assignment there is also the possibility to use the
Developer's Certificate of Origin sign-off:

https://gcc.gnu.org/dco.html

[Bug fortran/87326] [F18] Support the NEW_INDEX= specifier in the FORM TEAM statement

[weeks at iastate dot edu]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87326

--- Comment #7 from Nathan Weeks <weeks at iastate dot edu> ---
(In reply to anlauf from comment #6)
> (In reply to Nathan Weeks from comment #5)
> > (In reply to Brad Richardson from comment #3)
> > > Was there any more progress on this? I've just run into it.
> > > 
> > > FYI I'm trying implement a polymorphic send/receive:
> > > https://gitlab.com/everythingfunctional/communicator
> > 
> > The FSF copyright assignment ended up being an unexpectedly-difficult hurdle
> > at the time. I could try again if there is interest, though it would also
> > require some effort to rework the original patch for GCC 14. If another
> > contributor were willing to submit a clean-room implementation, that may be
> > more expedient.
> 
> Besides the copyright assignment there is also the possibility to use the
> Developer's Certificate of Origin sign-off:
> 
> https://gcc.gnu.org/dco.html

Is that an option in this case? I was originally advised to pursue a copyright
assignment:

https://gcc.gnu.org/pipermail/fortran/2019-January/051674.html

[Bug fortran/87326] [F18] Support the NEW_INDEX= specifier in the FORM TEAM statement

[anlauf at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87326

--- Comment #8 from anlauf at gcc dot gnu.org ---
(In reply to Nathan Weeks from comment #7)
> (In reply to anlauf from comment #6)
> > (In reply to Nathan Weeks from comment #5)
> > > (In reply to Brad Richardson from comment #3)
> > > > Was there any more progress on this? I've just run into it.
> > > > 
> > > > FYI I'm trying implement a polymorphic send/receive:
> > > > https://gitlab.com/everythingfunctional/communicator
> > > 
> > > The FSF copyright assignment ended up being an unexpectedly-difficult hurdle
> > > at the time. I could try again if there is interest, though it would also
> > > require some effort to rework the original patch for GCC 14. If another
> > > contributor were willing to submit a clean-room implementation, that may be
> > > more expedient.
> > 
> > Besides the copyright assignment there is also the possibility to use the
> > Developer's Certificate of Origin sign-off:
> > 
> > https://gcc.gnu.org/dco.html
> 
> Is that an option in this case? I was originally advised to pursue a
> copyright assignment:
> 
> https://gcc.gnu.org/pipermail/fortran/2019-January/051674.html

That requirement was changed in 2021:

https://gcc.gnu.org/pipermail/gcc/2021-June/236182.html

See also:

https://gcc.gnu.org/contribute.html

[Bug fortran/87326] [F18] Support the NEW_INDEX= specifier in the FORM TEAM statement

[weeks at iastate dot edu]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87326

--- Comment #9 from Nathan Weeks <weeks at iastate dot edu> ---
(In reply to anlauf from comment #8)
> (In reply to Nathan Weeks from comment #7)
> > (In reply to anlauf from comment #6)
> > > (In reply to Nathan Weeks from comment #5)
> > > > (In reply to Brad Richardson from comment #3)
> > > > > Was there any more progress on this? I've just run into it.
> > > > > 
> > > > > FYI I'm trying implement a polymorphic send/receive:
> > > > > https://gitlab.com/everythingfunctional/communicator
> > > > 
> > > > The FSF copyright assignment ended up being an unexpectedly-difficult hurdle
> > > > at the time. I could try again if there is interest, though it would also
> > > > require some effort to rework the original patch for GCC 14. If another
> > > > contributor were willing to submit a clean-room implementation, that may be
> > > > more expedient.
> > > 
> > > Besides the copyright assignment there is also the possibility to use the
> > > Developer's Certificate of Origin sign-off:
> > > 
> > > https://gcc.gnu.org/dco.html
> > 
> > Is that an option in this case? I was originally advised to pursue a
> > copyright assignment
> > 
> > https://gcc.gnu.org/pipermail/fortran/2019-January/051674.html
> 
> That requirement was changed in 2021:
> 
> https://gcc.gnu.org/pipermail/gcc/2021-June/236182.html
> 
> See also:
> 
> https://gcc.gnu.org/contribute.html

That's great news! I'll carve out some time to try to adapt the patch for GCC
14.