Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Nov 08 08:41
    vehre commented #742
  • Nov 07 04:59
    rouson commented #742
  • Nov 05 10:45
    hassaniriad edited #742
  • Nov 05 10:45
    hassaniriad opened #742
  • Oct 23 20:36
    rouson commented #624
  • Oct 23 20:31
    nathanweeks commented #624
  • Oct 23 15:10
    rouson commented #624
  • Oct 23 15:05
    nathanweeks synchronize #624
  • Oct 22 01:44
    nathanweeks commented #624
  • Oct 20 01:40
    rouson commented #624
  • Oct 20 01:36

    rouson on issue-733-impl-random-init

    (compare)

  • Oct 20 01:36
    rouson closed #740
  • Oct 20 01:36

    rouson on main

    Add random_init() and testcase. Add missing testcase's source. Fix refing static arrays. - Do… and 4 more (compare)

  • Oct 20 00:52

    rouson on issue-739-fix-seg-fault

    (compare)

  • Oct 19 15:15
    vehre commented #740
  • Oct 19 15:02
    rouson commented #741
  • Oct 19 15:00
    rouson commented #740
  • Oct 19 01:43
    everythingfunctional commented #741
  • Oct 19 01:11
    rouson commented #741
  • Oct 18 23:27
    rouson synchronize #740
Jerry DeLisle
@jerryd
Is there a way for this chat window to be out of browser? Is this chatroom private?
Izaak "Zaak" Beekman
@zbeekman
This chat is public
There's a native and phone app
We have a private chat for SI org
I'll look into whether non members can be added if you're interested
Izaak "Zaak" Beekman
@zbeekman
Yes, the private SI chat means you must be member of SI org, which for pricing reasons (which could be fixed... but...) right now it looks like you won't be able to join the private chat
Stefano Zaghi
@szaghi

Dear @zbeekman @rouson I have a problem with your great install.sh script. I am pushing my bosses to adopt opencoarrays, but they are strongly addicted to CentOS, and they are essentially paranoiac (root installation is not viable). The big issue is to install a recent gcc. Indeed, we have manually compiled installed gcc 6.2, but we have problem with gcc 6.3, thus I tried to exploit you script (that I used every week to update my local gcc-developing-trunk). However, I was not able to understand how to set the installer to point to 6.3 trunk instead of 6.1 (the default one). The syntax I use for the developing trunk is:

/install.sh -p gcc -b trunk -i /opt/gcc/bin/7.0.0

Can you let me know how to execute the script for installing 6.3 trunk?
Thank you very much for help!
Cheers

Damian Rouson
@rouson

Hi, Stefano. Thanks for your interest and especially for sharing with us your frequent use of the installation script. You can install any released versions using the --install-version or the equivalent -I option:

./install.sh -p gcc -I 6.3.0 -i /opt/gcc/bin/6.3.0

BTW, there exists a such a broad range of users: some refuse to use anything but a static Makefile; others prefer to use CMake; others use package management; others exclusively use the bash installation script install.sh. I believe we have to support as many installation options as possible and it's great to hear which option important users like you are choosing. Thanks for letting us know!
Stefano Zaghi
@szaghi

@rouson
Dear Damian,

BTW, there exists a such a broad range of users: some refuse to use anything but a static Makefile; others prefer to use CMake; others use package management; others exclusively use the bash installation script install.sh

:smile: I know. My bosses refuse all but CentOS... it is really a nightmare, not only for Fortran just think to LaTeX: using recent LaTeX packages, namely less old than 10 years becomes quickly a problem :smile:

Currently my workflow is strongly based on OpenCoarrays:

  • I use OpenCoarrays for CAF projects (mainly HASTY);
    • I use OpenCoarrays script to install (weekly/monthly) the latest gcc trunk for all Fortran projects;
  • I use Zaak's docker image for gcc nightly build (occasionally to check if some compiler's issues evolves);
  • now I will use OpenCoarrays script to install the latest gcc stable on my bosses' workstation :smile:

Thank you very much for the help, you rocks!

P.S. could you be interest on a very abstract designing of Fortran CFD libraries? I recently made important steps toward a really abstract CFD code exploiting many abstract libraries (obviously into which is FOODIE, FOODIE paper will be completed soon...)

Izaak "Zaak" Beekman
@zbeekman
Stefano, great news about FOODIE and your progress! Glad to hear that you're finding the installation script and other tools useful. Just FYI, as far as I know, you can either build a released GCC, OR the latest trunk, but you can't build, e.g., the latest GCC-6 branch... you have to use a release. (I just wanted to clarify that point, based on your original comment/question)
Stefano Zaghi
@szaghi
@zbeekman Dear Zaak, thank you for the clarification, you have anticipated my goal, build the latest 6-branch... :smile: Cheers
Izaak "Zaak" Beekman
@zbeekman
You could edit the script to build the 6 branch...
Damian Rouson
@rouson
@szaghi, yes, I'm very interested. It fits nicely with other things I'm working on. Please schedule some time for us to talk about what you're doing.
@zbeekman, if you're referring to the installer, it should be possible to install any (unreleased) branch, including non-trunk branches, using the --install-branch flag. For example, "./install.sh --install-branch gcc-6-branch" should install the pre-release GCC 6 branch. To see a list of all branches, use "./install.sh --list-branches gcc" or "./install.sh -B gcc".
Stefano Zaghi
@szaghi
@rouson Dear Damian, sure, soon you (and Zaak) will receive some email-spam from me :smile:
Damian Rouson
@rouson
@zbeekman, I was just looking through the commits since the last release. Most are related to documentation, but there was at least one that Andre committed on the core library (libcaf_mpi). How about we plan to get a new release out next week? FYI, I'm going to be at a workshop so I'll probably cancel this week's call.
Izaak "Zaak" Beekman
@zbeekman
Sounds good. I need to get in touch with Salvatore again about PSBLAS. I have a Homebrew formula for it that I need to submit (to Homebrew-science)
I found a bug in the bigint implementation that he has since fixed. If he can creat a new release then I can base the formula on my the latest release
Stefano Zaghi
@szaghi

Dear Damian ( @rouson @zbeekman ), as usual, today I tried your script to install the latest gcc 7.1 , but when I tried to list the available branches I got

┌╼ stefano@zaghi(09:56 AM Wed May 03) on master
├───╼ /opt/opencoarrays 20 files, 224Kb
└──────╼ ./install.sh --list-branches gcc
/opt/opencoarrays/prerequisites/build-functions/set_or_print_url.sh: line 49: version_to_build: unbound variable

Is this an issue of my env?
Is there an alternative to list available releases instead of branches?

I tried the following without success

╼ stefano@zaghi(09:58 AM Wed May 03) on master
├───╼ /opt/opencoarrays 20 files, 224Kb
└──────╼ ./install.sh -p gcc -I 7.1 -i /opt/arch/gcc/bin/7.1 -j 8
...
opt/opencoarrays/prerequisites/downloads /opt/opencoarrays
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--     0
curl: (9) Server denied you to change to the given directory
2017-05-03 07:58:52 UTC [     info] Cleaning up. Done
2017-05-03 07:58:52 UTC [     info] Cleaning up. Done

Cheers

Stefano Zaghi
@szaghi
Ok, I found my error, it works with ./install.sh -p gcc -I 7.1.0 -i /opt/arch/gcc/bin/7.1.0 -j 8, I missed the .0 in the release version. Is it possible to list the available releases? Cheers
chiensh
@chiensh
Hi All, I am new to Co-Array Fortran, I am checking the latest development of CAF standard, but found that the official site for CAF http://www.Co-array.org is no longer working , and OpenCoArray is the only active site that is still working for CAF. Can anyone tell me is the work on CAF standardisations dead or they have move to a different site? Thanks!
Damian Rouson
@rouson

Hi @szaghi. I don't know how easy it would be to list the available releases. Requesting the list of branches results in the issuance of the command "svn ls svn://gcc.gnu.org/svn/gcc/branches/". By contrast, releases are downloaded from an ftp server that is accessed via curl, wget, or ftp (in order from most preferred to least preferred). In order to list releases, I would have to sort out how to list the files in a particular directory of the ftp server using each of the aforementioned three methods. I recommend using the command "./install.sh -U gcc" to list the default URL for downloading GCC (or replace GCC with the name of any other package that the installer knows how to build). Once you have that URL, you can visit the server in a browser to see the available packages.

With all the said, seeing the list will be of limited value if you're planning to use the compiler with OpenCoarrays. For several years to come (certainly at least 2-3), it will always be advisable to use OpenCoarrays with the latest GCC release. Until recently, that meant using 6.3.0. However, GCC 7.1.0 was released about a month ago as you probably know and just yesterday @zbeekman released OpenCoarrays 1.9.0 with experimental support for some exciting new features for users of GCC 7.1.0. Zaak or I will explain more in an email to the OpenCoararys mailing list sometime within the next 24 hours so watch for that if you're on the OpenCoararys Google Group mailing list.

Damian Rouson
@rouson
@chienesh I don't recall who owned www.co-array.org, but I don't think it was ever "official" as the official standards body for Fortran (including the standardized coarray features) is the ISO WG5 site. The most official resource is the draft version of the Fortran 2015 standard, which is available on the WG5 site here. With the support of OpenCoarrays, gfortran supports most coarray features with the only major exception being teams. Also, it's worth noting that even though "coarray Fortran" is a popular term for historical reasons, it's also possible to accomplish quite a lot by way of parallel programming without ever declaring or using a coarray. For some applications, any communication needs can be covered by the Fortran 2015 collective subroutines (co_broadcast, co_sum, co_max, co_min, and co_reduce). I highly recommend reading about those subroutines in the standard and using them whenever they are applicable. The can accomplish parallel communication and computation in a very efficient manner in shared or distributed memory and the arguments to these subroutines do not need to be declared as coarrays.
chiensh
@chiensh
Thank you Damian! I was also checking if there is any plan for collective routines in future, and you have answered my question. BTW, although www.co-array.org has never been the official CAF site, but it was referenced in the homepage of J3 Fortran Committee and wikipedia, so I think it needed to be clarified.
Damian Rouson
@rouson
Interesting. I didn't realize that. FYI, the Cray compiler also supports the Fortran 2015 collective subroutines. And as you might know, Intel's compiler reached full Fortran 2008 compliance this year with the beta release of version 18. I assume that means they'll start on Fortran 2015 parallel features after the 18 (they already support many if not all of the Fortran 2015 C-interop features so the parallel features should be next). Collective procedures are probably the easiest of the Fortran 2015 parallel features because they can be implemented as thin wrappers around MPI_Reduce. Let's hope we can have three Fortran 2015 compilers within 2-3 years.
Jeff Hammond
@jeffhammond
it is true that Fortran 2015 coarray collectives are easy to implement, particularly in compilers that use MPI as the coarray runtime. i don't know when Intel plans to implement these, but in general, the compiler team prioritizes features based upon customer demand. posting on the Intel forums or filing support tickets is the right way to create this demand (in addition to setting procurement requirements, which is not an option for most folks, obviously).
(says Jeff who works for Intel but does not speak for Intel )
Izaak "Zaak" Beekman
@zbeekman
I'm thinking it may not be too hard to get a binder notebook up and running with a coarray Fortran kernel. That would be pretty darn cool.
Stefano Zaghi
@szaghi

Dear @zbeekman and @rouson ,

I know that it is impossible to support all OS... but I would like to report that OpenCoarrays install.sh seems to fail on CentOS (an OS that is quite ancient).

Here my log

[root@broglia-6 OpenCoarrays]# ./install.sh -p gcc -b trunk -i /opt/gcc/bin/8.0.0 -j 8 -d
...
2017-06-05 10:35:13 UTC [     info] build_path="/opt/gcc/src/OpenCoarrays"/prerequisites/builds
+ export build_script=/opt/gcc/src/OpenCoarrays/prerequisites/build.sh
+ build_script=/opt/gcc/src/OpenCoarrays/prerequisites/build.sh
+ info 'build_script="/opt/gcc/src/OpenCoarrays"/prerequisites/build.sh'
+ '[' 7 -ge 6 ']'
++ _fmt info
++ local 'color_debug=\x1b[35m'
++ local 'color_info=\x1b[32m'
++ local 'color_notice=\x1b[34m'
++ local 'color_warning=\x1b[33m'
++ local 'color_error=\x1b[31m'
++ local 'color_critical=\x1b[1;31m'
++ local 'color_alert=\x1b[1;33;41m'
++ local 'color_emergency=\x1b[1;4;5;33;41m'
++ local colorvar=color_info
++ local 'color=\x1b[32m'
++ local 'color_reset=\x1b[0m'
++ '[' '' = true ']'
++ [[ xterm-256color != \x\t\e\r\m* ]]
++ '[' -t 1 ']'
+++ date -u '+%Y-%m-%d %H:%M:%S UTC'
+++ printf '[%9s]' info
++ echo -e '2017-06-05 10:35:13 UTC \x1b[32m[     info]\x1b[0m'
+ echo '2017-06-05 10:35:13 UTC [     info] build_script="/opt/gcc/src/OpenCoarrays"/prerequisites/build.sh'
2017-06-05 10:35:13 UTC [     info] build_script="/opt/gcc/src/OpenCoarrays"/prerequisites/build.sh
+ source /opt/gcc/src/OpenCoarrays/prerequisites/stack.sh
+ stack_new dependency_pkg
+ : dependency_pkg
+ stack_exists dependency_pkg
+ : dependency_pkg
+ eval '_i=${_stack_dependency_pkg_i:-}'
++ _i=
+ [[ -z '' ]]
+ return 1
++ uname
+ [[ Linux == \D\a\r\w\i\n ]]
+ eval 'declare -ag _stack_dependency_pkg'

I have trimmed out a lot of hopefully non useful log-lines before the very end.

On the same CentOS workstation I have trouble to compile manually gcc...

Cheers

Izaak "Zaak" Beekman
@zbeekman
Hi Stefano/@szaghi, first of all what does /usr/bin/env bash --version say? Also, can you please include the entire log? I'm not seeing where the error occurred... Damian created a script for use on the ParaTools HPC Linux VM which is also CentOS based, but I'm not sure it has all the same features as ./install.sh (specifying individual packages to build etc.). You could try your luck invoking prerequisites/build.sh ... directly as in https://github.com/sourceryinstitute/OpenCoarrays/blob/master/developer-scripts/hpclinux-install.sh#L64-L69 but you may have trouble resolving the pre-requisite dependencies, I'm not sure....
I also find that sometimes I need to build an intermediate compiler to get a very modern GCC built...
Stefano Zaghi
@szaghi

@zbeekman

Sorry for my delay.

The bash says

(riccardo@broglia-6)-(0)-(05:51 PM Tue Jun 06)
(/opt/gcc/bin)-(2 files, 16Kb)-> /usr/bin/env bash --version
GNU bash, version 4.1.2(2)-release (x86_64-redhat-linux-gnu)
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>

This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

The complete log of ./install.sh is too long to paste here, can I send it via email?

Anyhow, I manged to install gcc & Co. manually on this CentOS workstation (and in our small cluster that is also CentOS based):

/opt/gcc/bin/ 
├── 7.1.0 
│   ├── bin 
│   ├── include 
│   ├── lib 
│   ├── lib64 
│   ├── libexec 
│   ├── module.sh 
│   └── share 
└── 8.0.0 
   ├── bin 
   ├── include 
   ├── lib 
   ├── lib64 
   ├── libexec 
   ├── module.sh 
   └── share

/opt/mpi/bin/mpich/3.2.0/gnu/ 
├── 7.1.0 
│   ├── bin 
│   ├── include 
│   ├── lib 
│   ├── module.sh 
│   └── share 
└── 8.0.0 
   ├── bin 
   ├── include 
   ├── lib 
   ├── module.sh 
   └── share

FYI, I had not need to build an intermediate gcc for the 7.x and 8.x trunks: this CentOS provides gcc 4.x and it was enough to build them. Probably something is changed with respect 6.x trunks because I remember that I had more problem to build 6.x from 4.x than 7/8.x from 4.x. The only trick was to populate contrib prerequisites before configure/make (that was not necessary in my other workstation with a more decent linux distro...).

My best regards.

Izaak "Zaak" Beekman
@zbeekman
sure, email me the logs at zbeekman@gmail.com
Izaak "Zaak" Beekman
@zbeekman

Hi @/all, Just wanted to let you know that you can now try OpenCoarrays in the cloud via Binder. It is implemented as a kernel for Jupyter over at https://github.com/sourceryinstitute/jupyter-CAF-kernel. You can launch the binder (which also has python, Julia, and R kernels installed) using this button: Binder.

Navigate to the index.ipynb file to run a demo. Or create a new notebook using the Coarray Fortran kernel and run your own experimental code, after seeing a few tutorial details in the index.ipynb file. If you just want to skip straight to that file use this link: https://bit.ly/TryCoarrays. To get to the full on binder instance, same as the button, go to https://bit.ly/CAF-Binder

Jeff Hammond
@jeffhammond
Why in Homebrew does OpenCoarrays say it requires "mpi" but then refuses to accept the one true MPI implementation ("mpich")? Particularly given how buggy Open-MPI has been w.r.t. RMA over the years, it's pretty shocking that you all would rely on it anywhere.
jrhammon-mac01:github jrhammon$ brew info opencoarrays
opencoarrays: stable 1.9.0 (bottled), HEAD
Open-source coarray Fortran ABI, API, and compiler wrapper
http://opencoarrays.org
Not installed
From: https://github.com/Homebrew/homebrew-core/blob/master/Formula/opencoarrays.rb
==> Dependencies
Build: cmake ✔
Required: gcc ✔
==> Requirements
Required: fortran ✔, mpi ✘
==> Options
--without-test
    Skip build time tests (not recommended)
--HEAD
    Install HEAD version
==> Installing dependencies for opencoarrays: libevent, open-mpi
==> Installing opencoarrays dependency: libevent
==> Downloading https://homebrew.bintray.com/bottles/libevent-2.1.8.sierra.bottle.tar.gz
######################################################################## 100.0%
==> Pouring libevent-2.1.8.sierra.bottle.tar.gz
^C
jrhammon-mac01:github jrhammon$ brew install mpich && brew install opencoarrays
==> Downloading https://homebrew.bintray.com/bottles/mpich-3.2_3.sierra.bottle.tar.gz
######################################################################## 100.0%
==> Pouring mpich-3.2_3.sierra.bottle.tar.gz
==> Using the sandbox
🍺  /usr/local/Cellar/mpich/3.2_3: 885 files, 14.2MB
==> Installing dependencies for opencoarrays: libevent, open-mpi
==> Installing opencoarrays dependency: libevent
==> Downloading https://homebrew.bintray.com/bottles/libevent-2.1.8.sierra.bottle.tar.gz
Already downloaded: /Users/jrhammon/Library/Caches/Homebrew/libevent-2.1.8.sierra.bottle.tar.gz
==> Pouring libevent-2.1.8.sierra.bottle.tar.gz
==> Using the sandbox
🍺  /usr/local/Cellar/libevent/2.1.8: 847 files, 2.2MB
==> Installing opencoarrays dependency: open-mpi
Error: Cannot install open-mpi because conflicting formulae are installed.
  mpich: because both install mpi__ compiler wrappers

Please `brew unlink mpich` before continuing.

Unlinking removes a formula's symlinks from /usr/local. You can
link the formula again after the install finishes. You can --force this
install, but the build may fail or cause obscure side-effects in the
resulting software.
I mean, there's a reason that ARMCI-MPI in Travis CI has the XFAIL list that it does... (https://travis-ci.org/jeffhammond/armci-mpi)
Damian Rouson
@rouson
@szaghi My apologies for not responding sooner. I just came out of a stretch of insane travel to 5 countries in about 8 weeks for both business and family travel and I'm just digging out from under about 2,000 unread emails. I have seen problems with the installer with older Fedora-based distributions. The problems I've seen relate to the stack-management code that I borrowed from http://brizzled.clapper.org/blog/2011/10/28/a-bash-stack/. I believe that's the same code that failed on CentOS for you. I have found that it works on more recent distributions so I decided not to investigate further. I would be glad to review a pull request if you or another user wants to fork OpenCoarrays and submit a fix. Otherwise, I'm hopeful that most people with either be able to update to a newer release of the Linux distribution or will use package management such as linuxbrew.
Stefano Zaghi
@szaghi

@rouson Dear Damian, do not worry, I know how much busy you are. For the CentOS we are very in trouble: the cluster front-end has a more recent CentOS with respect other nodes thus also the manual compilation of gcc is problematic (it works with some tricks on the front-end, but nope into the nodes...), not only the installation of opencoarrays. Unfortunately, I am also very busy for an open public contest that will end in August (all my work is almost "freeze") thus I cannot try to fix our cluster issues neither try to provide a patch for OpenCoarrays for supporting such an aged OS. Anyhow, thank you very much for having found the time to replay to me, you are great!

Cheers.

P.S. I read about the new initiative of the standard committee for collecting users suggestions: Jacob ( @jacobwilliams ) has started a GitHub repository for collecting such items https://github.com/Fortran-FOSS-Programmers/Fortran-202X-Proposals . It would be wonderful if you and other committee members will "put an eye" on it (I know that Van Snyder has many many proposals, it would be great if he will join us on GitHub).

Jeff Hammond
@jeffhammond
@szaghi You can submit the compilation of GCC as a batch job to build it on the compute nodes.
Stefano Zaghi
@szaghi
@jeffhammond Hi Jeff, yes you are right, but the problem is that I have to find how to build gcc on the nodes and now I am too much busy. On the nodes, it seems that before building gcc 6,.x I have to build gcc 5.x by means of the gcc 4.x provided by the system... this needs some tests that now I cannot do. On the contrary, the frontend builds gcc 6.x straightforward. Why on the Earth we use CentOS... Anyhow, thank you very much! Cheers
Jeff Hammond
@jeffhammond
@szaghi If your issue is figuring how to build GCC non-interactively, please consider using my script for this. https://github.com/jeffhammond/HPCInfo/blob/master/buildscripts/gcc-release.sh#L58 is the only line you should need to edit, according to which version(s) you want.
Jeff Hammond
@jeffhammond
if you want GCC 6.4.0, change bz2 to xz until i push a fix.
those are boot-strapped builds so they should not require a new version of GCC. i use that on CentOS 6.6 with GCC 4.4.7 system compiler.
Stefano Zaghi
@szaghi
Hi @jeffhammond thank you for sharing your script, tomorrow I'll try it. Cheers
Izaak "Zaak" Beekman
@zbeekman
@jeffhammond sorry for the slow response regarding your Homebrew inquiry. I have seen this before and been mystified by it. When you do brew info mpich does it show mpich is installed? I have a Brewfile that you can use with brew bundle. First brew tap homebrew/bundle && brew bundle # Brewfile must be in CWD
Izaak "Zaak" Beekman
@zbeekman
hmmm I may have to add a build-from-source argument to the Brewfile... Your problem stems from the fact that Homebrew defaults to OpenMPI even though, as you point out, it has serious RMA problems. If you can cite compelling reasons and evidence of it's dysfunction, I would suggest opening an issue on the main Homebrew repo. I will weigh in with my support. When you install OpenCoarrays, adding a --build-from-source argument should alleviate your issues and allow it to use MPICH. Homebrew bottles all formulae by default, and using it's preferred/default MPI: OpenMPI. So, when homebrew builds binaries for OpenCoarrays it defaults to linking against OpenMPI. So, to satisfy the MPI requirement locally, without OpenMPI installed, you need to build OpenCoarrays from source by passing --build-from-source to brew install --build-from-source OpenCoarrays
Izaak "Zaak" Beekman
@zbeekman
OpenCoarrays 1.9.1 has been released and includes many bug fixes: https://github.com/sourceryinstitute/OpenCoarrays/releases/latest

Github Releases (by Asset) Build Status license Twitter URL

Bug fixes

  • #325 install.sh will help user download and install Xcode command line tools (CLT) on Mac OS which is needed to compile code on Macs if it is missing or excessively outdated
  • #378 mpirun changed to mpiexec and mpif90 changed to mpifort, consistent with MPI standard recommendations
  • #398 fix some erroneous internal library calls when exceptions are encountered
  • #399 fix allocation of allocatable components of coarray derived types
  • #402 increase portability of install script install.sh by removing dependency on tree command
  • #404 fix issue where install.sh was ignoring user specified -m/--with-cmake CMake location
  • #406 use secure https/encrypted sources for fetching and installing prerequisites to help mitigate the possibility of a man-in-the-middle (MITM) attack
  • #408 switch to downloading the gzipped GCC archive rather than the bz2 because gzip is more common/portable and because bz2 compressed GCC archives seem to have disappeared for some recent releases on GCC mirrors
  • #411 fix bug causing event_post to hang when going over the network (multiple nodes)
  • #422 clarify runtime error messages for partially or un-implemented
  • Corrected logic to control under which circumstances certain tests are run that may only work correctly under GFortran 6 or GFortran 7

Enhancements

  • #410 add option --disable-bootstrap to install.sh to help speed builds of GCC when bootstrapping is not required because a recent GCC is performing the build
  • #424 add option to install.sh to download the requested package from a user specified URL
  • Prevent developer's advanced Makefiles and GASNet directory from being distributed with release tarballs

Installation

Please see the installation instructions for more details on how to build and install this version of OpenCoarrays


GitHub forks GitHub stars GitHub watchers Twitter URL