The first error message in my previous email led me to the following
constraint:
“*C1130* A *variable-name *that appears in a LOCAL or LOCAL_INIT
*locality-spec *shall not have the ALLOCATABLE, INTENT (IN), or OPTIONAL
attribute, shall not be of finalizable type, shall not have an allocatable
ult
I recently built the master branch of Iain's fork of gcc in order to test
the support for locality specifiers. I have verified that the branch I
built contains the commit mentioned in this email thread
20b8500cfa522ebe0fcf756d5b32816da7f904dd. The code below isn't designed to
do anything useful
On Tue, Dec 17, 2024 at 20:05 Steve Kargl
wrote:
> On Mon, Dec 16, 2024 at 04:53:42AM -0800,
Or, perhaps, you care to qualify your generalization?
Thanks for asking. When I tried using kind type parameters on derived
types with gfortran a few months ago, I gave up because the issues appeared
to
I don’t think the standard requires providing the stop code to the OS, but
it recommends doing so. So this is a great idea. Thanks for working on
coarray features.
Damian
On Thu, Dec 19, 2024 at 04:14 Andre Vehreschild wrote:
> Hi all,
>
> attached patch fixes a rather old open issue, that I
This is a big deal, Andre! Thanks for working on this patch. I have some
test code that I can dig up if that’s helpful. Have you tested with nested
derived type components, i.e., allocatable components that are themselves
derived types that have allocatable components?
The need for this featur
I wonder if a relatively easy starting point would be enabling the
declaration of do concurrent construct variables:
do concurrent (integer :: i = 1:n)
It’s a minor convenience and less exciting than adding locality specifiers
but possibly a good first exercise.
Damian
On Thu, Feb 23, 2023 at
On Tue, Nov 2, 2021 at 8:56 AM Sandra Loosemore
wrote:
>
> ... I will hold off on that if it's going to cause problems.
>
> Thanks for taking on this task, Sandra. I'm not aware of the technical
issues around mark-up formatting and the transition that's happening, but I
hope nothing holds up a l
I've been seeing similar messages to this one for quite some time now -- I
think ~1 year. I don't often use unpack so there are likely many other
causes too. I haven't take the time to isolate them, but if I can do so
easily, I'll submit reports.
Damian
On Mon, Sep 28, 2020 at 2:12 PM Tobias Bu
Could someone please update the Fortran 2018 status page on the wiki
to reflect this patch? I would volunteer to do it myself, but I've
tried on at least 3 occasions (including today) to set up an account
or generate a new password and every attempt fails with a warning that
I'm being locked out b
On Wed, Jan 9, 2019 at 3:08 PM Thomas Koenig wrote:
>
>
> Thanks a lot for this! Looking at what we are currently
> finishing, I think we will be quite close to F2008 conformance
> when gcc 9 comes out, modulo a few bugs, of course.
And because ISO_Fortran_binding.h is part of Fortran 2018, this
On Fri, Sep 21, 2018 at 9:25 AM Jerry DeLisle wrote:
> The actual library source code is contained mostly in one source file.
There are as many files as there are options for the underlying
parallel programming
model. The default is MPI, but I've co-authored conference papers last year
and this
On Thu, Sep 20, 2018 at 1:01 PM Thomas Koenig wrote:
>
> We addressed integrating OpenCoarray into the gcc source tree at the
> recent Gcc summit during the gfortran BoF session.
>
I agree with keeping it as a separate code base, but comments from some
gfortran developers on the gfortran mailing
On Wed, Sep 19, 2018 at 3:30 PM Andrew Stubbs wrote:
>
> If you want to port your tool to GCN that would be cool, but I suspect
> non-trivial.
>
To clarify, OpenCoarrays is not a tool. It is the parallel ABI required to
create executable programs capable of executing in multiple images as
requi
Has this been tested in multi-image execution using OpenCoarrays? If not,
I would be glad to assist with installing OpenCoarrays so that it can be
part of the testing process.
On a related note, two Sourcery Institute developers have attempted to edit
the GCC build system to make the downloading
Thank you!
Damian
On May 17, 2018 at 12:32:19 AM, Thomas Koenig (tkoe...@netcologne.de) wrote:
> Hi Damian,
>
> Partial support is provided for Fortran 2018 teams, which are
> hierarchical
> subsets of images that execute independently of other image subsets.
>
>
> Committed.
>
> Regards
**PING**
Could someone either approve and apply this or explain to me how to do so? I
don’t have commit rights so I don’t think I can do it.
Damian
On May 2, 2018 at 11:22:02 AM, Damian Rouson (dam...@sourceryinstitute.org)
wrote:
The patch below includes a description of a new feature in
The patch below includes a description of a new feature in gfortran for
inclusion in the GCC 8 changes.html file. I don’t have commit rights. Could
someone approve and apply this? Thanks.
Damian
cvs diff: Diffing .
Index: changes.html
are four. I was mistaken when I wrote that there are three.
Damian
On February 21, 2018 at 12:56:05 PM, Janne Blomqvist
(blomqvist.ja...@gmail.com) wrote:
On Wed, Feb 21, 2018 at 10:18 PM, Damian Rouson
wrote:
>
>
>
>
> On February 21, 2018 at 11:35:47 AM,
On February 21, 2018 at 11:35:47 AM, Janne Blomqvist
(blomqvist.ja...@gmail.com(mailto:blomqvist.ja...@gmail.com)) wrote:
> PING
>
> Is anybody planning to work on this on the opencoarrays side? Or do
> you prefer that this is just committed and you can sort it out on your
> own sche
Hi Andre,
Thanks for your latest work on CAF features. Could you let us know whether
this commit should be tested against the OpenCoarrays master branch or another
branch? With the master branch, I get one test failure (not counting two known
teams failures that are actually false negatives t
I’ll try applying the patch and testing it. I have about a 50% success rate
with getting patches to apply cleanly. Is this available on an svn or git
branch that I can just checkout rather than attempting to apply the patch? I
find that process to be much more reliable.
Going forward, ple
On January 24, 2018 at 1:29:12 PM, Steve Kargl
(s...@troutmask.apl.washington.edu) wrote:
Yes, thanks, Paul. Unfortunately, I've run out of time.
Damian, GCC is in stage 3, we need to wait for approval
from the release manager (aka Jakub) before committing
the patch.
Will do.
Damia
anuary 2018 at 05:45, Steve Kargl
wrote:
> I'm heading out of town for a meeting at the end of
> week, so gfortran patches/reviews are on hold at the
> moment. If someone else wants to step up to review
> the patch, I won't object.
>
> --
> steve
>
, Jan 19, 2018 at 10:33 AM, Steve Kargl
wrote:
> On Fri, Jan 19, 2018 at 09:18:14AM -0800, Damian Rouson wrote:
>> Thanks for catching that, Steve, and for responding, Alessandro.
>>
>> Anything else?
>>
>
> I've only just started to look at the
Thanks for catching that, Steve, and for responding, Alessandro.
Anything else?
Damian
On January 19, 2018 at 9:17:03 AM, Alessandro Fanfarillo (elfa...@ucar.edu)
wrote:
Yes, definitively ar->team.
On Fri, Jan 19, 2018 at 8:36 AM, Steve Kargl
wrote:
> index 882fe577b76..b4baf5be554 100644
remains one big,
dissertation-worthy project in handling the use of teams in the presence of
failed images.
Ok for trunk?
Damian
2018-01-18 Damian Rouson
Alessandro Fanfarillo
Partial support for Fortran 2018 teams features.
* array.c (gfc_match_array_ref): add
the above script to
give an option for multithreaded builds to speed things up quite a bit.
Damian
On January 8, 2018 at 6:03:26 PM, Steve Kargl
(s...@troutmask.apl.washington.edu) wrote:
On Mon, Jan 08, 2018 at 05:33:01PM -0800, Damian Rouson wrote:
> I’ll be glad to test with -fcoarray=
I’ll be glad to test with -fcoarray=lib -lcaf_mpi with two caveats:
1. My turnaround time will probably usually be 48-72 hours for such tests.
2. I don’t monitor this mailing list very closely so I might miss similar
requests unless they are also submitted as issues on the OpenCoarrays GitHub
would confirm that there are no issues
with applying the patch to 7-branch.
Thanks for all the help.
Paul
On 28 December 2017 at 19:58, Damian Rouson
wrote:
> I applied the patch the trunk and confirmed that it doesn’t break any
> previously
> passing OpenCoarrays tests
On January 2, 2018 at 10:02:01 AM, Paul Richard Thomas
(paul.richard.tho...@gmail.com(mailto:paul.richard.tho...@gmail.com)) wrote:
> Somewhere, I have a list of situations where finalization is required
> but not yet implemented. I'll dig it out and post it on the list.
PR 37336 has a
I applied the patch the trunk and confirmed that it doesn’t break any previously
passing OpenCoarrays tests. Is that sufficient or should I also try applying
the
patch to the 7 branch?
Damian
Thanks for the additional information Thomas. It sounds like I should test
Paul’s patch. I should be able to do so today and will post the results by
tomorrow. I’m adding OpenCoarrays developer Zaak Beekman to the cc and
attaching the patch again in case he wants to try it as well.
Zaak, the
Hi Paul,
Does breaking binary compatibility simply mean that CAF codes will need to be
recompiled (which is fine) or does it mean that there will need to be work done
on OpenCoarrays to support the changes in this patch (which is unlikely to
happen soon without new contributors to OpenCoarray
On October 21, 2017 at 11:17:49 AM, Bernhard Reutner-Fischer
(rep.dot@gmail.com(mailto:rep.dot@gmail.com)) wrote:
>
> + die "Invoking wget and curl in the 'download_prerequisites' script failed."
>
> I suggest "Neither wget nor curl found, cannot download tarballs.”
Thanks for th
On October 23, 2017 at 3:54:22 AM, Richard Biener (richard.guent...@gmail.com)
wrote:
On Sat, Oct 21, 2017 at 2:26 AM, Damian Rouson
wrote:
>
> Hi Richard,
>
> Attached is a revised patch that makes the downloading of Fortran
> prerequisites optional via a new --no-fortra
the interim.
Ok for trunk?
Damian
On September 21, 2017 at 12:40:49 AM, Richard Biener
(richard.guent...@gmail.com(mailto:richard.guent...@gmail.com)) wrote:
> On Wed, Sep 20, 2017 at 10:35 PM, Damian Rouson
> wrote:
> > Attached is a patch that adds the downloading of gfortran p
Attached is a patch that adds the downloading of gfortran prerequisites
OpenCoarrays and MPICH in the contrib/download_prerequisites script. The patch
also provides a useful error message when neither wget or curl are available on
the target platform. I tested this patch with several choices f
o the list with further thoughts on this.
Best Regards,
___
Damian Rouson, Ph.D., P.E.
President, Sourcery Institute
www.sourceryinstitute.org(http://www.sourceryinstitute.org)
+1-510-600-2992 (mobile)
On September 6, 2017 at 6:04:47 AM, Paul Richard T
Resending as plain text:
On April 12, 2017 at 3:03:19 PM, Jeff Law
(l...@redhat.com(mailto:l...@redhat.com)) wrote:
> >
> > 2017-04-05 Damian Rouson
> >
> > * download_prerequisites (md5_check): New function emulates Linux
> > 'md5 --check&#
. macOS ships with curl but not wget.
Tested on macOS and Lubuntu and Fedora Linux distributions.
Ok for trunk?
Damian
2017-04-05 Damian Rouson
* download_prerequisites (md5_check): New function emulates Linux
'md5 --check' on macOS. Modified script for macOS com
On April 4, 2017 at 9:48:23 AM, Jerry DeLisle
(jvdeli...@charter.net(mailto:jvdeli...@charter.net)) wrote:
> Gerald, (or who does this)
>
> Since shared memory parallel programming with Fortran is now a Standard
> feature
> of the language, we would like to support full parallelism th
Resending as plain text (although now I realize my reply is at least partially
redundant since reading Andre’s email):
On April 4, 2017 at 10:44:09 AM, FX
(fxcoud...@gmail.com(mailto:fxcoud...@gmail.com)) wrote:
> > We choose mpich as a default only because it is very stable.
>
> Why are wh
On August 27, 2016 at 1:15:51 PM, Janne Blomqvist
(blomqvist.ja...@gmail.com(mailto:blomqvist.ja...@gmail.com)) wrote:
>
> Anyway, a small nit I found was the function st_set_nml_var in
> libgfortran. This is an exported function, and thus part of the ABI.
> So you cannot add arguments to i
The patch below expands the list of new Fortran support for the GCC 6 Release
Series Changes, New Features, Fixes page at
.https://gcc.gnu.org/gcc-6/changes.html. Please let me know whether this is
acceptable and will be applied.
Damian
--- original.html 2016-05-03 22:25:23.0 -0
> On Apr 3, 2016, at 3:04 PM, Andre Vehreschild wrote:
>
> Hi Damian,
>
> To say it quite bluntly, I don't know. I took care of the ICE only, but I
> don't have a deeper understanding of the coarray usage, therefore I can't
> answer your question.
Hi Andre,
No problem. Thanks for the quick
; Bootstrapped and regtested ok on x86_64-linux-gnu/F23. Ok for trunk?
>
> The patch also applies (with a small delta) to gcc-5 w/o any
> regressions. Ok for gcc-5-branch?
>
> Regards,
> Andre
> --
> Andre Vehreschild * Email: vehre ad gmx dot de
>
Damian Rouson, Ph.D., P.E.
President, Sourcery Institute
http://www.sourceryinstitute.org
+1-510-600-2992 (mobile)
> On Nov 25, 2015, at 9:24 AM, Alessandro Fanfarillo
> wrote:
>
> Dear all,
>
> in attachment the previous patch compatible with the current trunk.
> The patch also includes the changes introduced in the latest TS 18508.
>
> Built and regtested on x86_64-pc-linux-gnu.
>
> PS: I will add the
I love this idea and had similar thoughts as well.
:D
Sent from my iPhone
> On Jul 24, 2015, at 1:06 AM, Paul Richard Thomas
> wrote:
>
> Dear Mikael,
>
> It had crossed my mind also that a .mod and a .smod file could be
> written. Normally, the .smod files are produced by the submodules
> On Jul 23, 2015, at 12:46 AM, Paul Richard Thomas
> wrote:
>
> Since all the private entities in a module have to be transmitted to
> their descendant submodules, whilst keeping them hidden from normal
> use statements, I have chosen to write the module file as usual and
> add a second part
Thank you!
Damian
> On Jul 17, 2015, at 9:50 AM, Mikael Morin wrote:
>
> Le 17/07/2015 11:02, Mikael Morin a écrit :
>> Le 16/07/2015 16:34, Damian Rouson a écrit :
>>> Alternatively, if it’s easy, please feel free to add the directives and
>>> commit.
>
> On Jul 15, 2015, at 8:58 AM, Mikael Morin wrote:
>
> The patch itself looks good to me.
> A ChangeLog entry should be provided with it.
> The test is missing the usual dejagnu pattern matching directives to
> check the generated code.
> Do you have commit rights?
Hi Mikael,
Thanks for the q
Group compilers.
Damian Rouson, Ph.D., P.E.
Founder & President, Sourcery, Inc.
510-600-2992 (mobile)
http://www.sourceryinstitute.org
http://rouson.youcanbook.me
> On Jun 5, 2015, at 4:04 AM, Andre Vehreschild wrote:
>
> Hi all,
>
> attached
52 matches
Mail list logo
