On Mon, Jun 13, 2022 at 8:27 AM Jonathan Wakely via Fortran <
fort...@gcc.gnu.org> wrote:
>
> It doesn't include them, but they are standard system packages that
> everybody can install without downloading the sources and building
> them from scratch.
unless the person is on a system on which th
On Mon, Jun 13, 2022 at 8:27 AM Jonathan Wakely via Fortran <
fort...@gcc.gnu.org> wrote:
>
> Yes, it does that, but takes 400 lines of shell script to do so.
>
> If you want "relatively easy ways to build GCC painlessly" then you
> can do it with nine lines of shell commands.
>
> Or in about 80,
I assume it’s too late for new project ideas. I’m adding Milan Curcic in
cc to confirm.
Damian
On Wed, Mar 9, 2022 at 18:09 Jerry D via Fortran
wrote:
> Perhaps someone could work on completing and merging the shared memory
> (native) fortran coarrays branch.
>
> Regards,
>
> Jerry
>
> On 3/9/
Thanks to you and Janne for the thoughtful replies. I understand better
the immediate goals now.
Damian
On Thu, Sep 19, 2019 at 08:31 Richard Earnshaw (lists) <
richard.earns...@arm.com> wrote:
> On 19/09/2019 13:04, Janne Blomqvist wrote:
> > On Tue, Sep 17, 2019 at 3:02 PM Richard Earnshaw (l
On Thu, Sep 19, 2019 at 5:04 AM Janne Blomqvist
wrote:
>
> One thing that's unclear to me is how should I actually make my stuff
> appear in the public repo? Say I want to work on some particular
> thing:
>
This is essentially a git workflow question. A simple and useful workflow
to consider is
On May 2, 2018 at 9:43:23 AM, Jakub Jelinek
(ja...@redhat.com(mailto:ja...@redhat.com)) wrote:
> There is no deadline on gcc-*/changes.html changes, it can be changed
> whenever changes for it are acked. Of course it is always better to
> do it before the release if possible.
>
Could some
On April 4, 2018 at 1:12:25 AM, Richard Biener
(richard.guent...@gmail.com(mailto:richard.guent...@gmail.com)) wrote:
> In that case user programs compiled with -fcoarray=lib are but gfortran
> or libgfortran itself is not linked against OpenCoarrays?
Yes. OpenCoarrays produces the parallel ru
On April 3, 2018 at 1:36:37 AM, Richard Biener (richard.guent...@gmail.com)
wrote:
You probably only want a new target_module for the MPI library. Note
it's name has to match that of the directory containing the sources
which
as far as I see is 'mpich', not 'libmpi'.
Thanks! I’ll ask Daniel
All,
Jerry DeLisle, Daniel Celis Garza, and I would greatly appreciate feedback on
our approach to patching the GCC build system to build MPICH and OpenCoarrays
after it builds gfortran (gfortran requires MPI and OpenCoarrays to support the
parallel features of Fortran 2008 and Fortran 2018).
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 January 26, 2017 at 9:12:36 AM, Jerry DeLisle
(jvdeli...@charter.net(mailto:jvdeli...@charter.net)) wrote:
> On 01/26/2017 05:25 AM, FX wrote:
>
> > - I am a bit surprised by the complexity of the script… couldn’t we provide
> > a Makefile for opencoarrays, to be compatible with our other buil
Could someone please tell me how to edit or submit edits for the GCC 6 release
notes at https://gcc.gnu.org/gcc-6/changes.html? Specially, the listed Fortran
improvements are missing several significant items. I signed the copyright
assignment in case hat helps.
Damian
I'm interested in contributing to the gfortran compiler. Please send
me any forms or instructions I need to follow regarding copyright
assignment.
Damian Rouson
+1-510-600-2992 (mobile)
14 matches
Mail list logo
