I am really confused but from what I can figure out so far, this project is
of similar practical value to the Brainf**k programming language.
Jeff
On Wed, Dec 21, 2016 at 6:54 AM, Jeff Squyres (jsquyres) <jsquyres(a)cisco.com
> wrote:
> Fortran people totally must vote:
>
> https://docs.google.com/forms/d/e/1FAIpQLSfkR0lXwzwc-
> p7AMGpGKUvjy8POT5X11QHnR96BnVnYSP5NWQ/viewform
>
> (This is safe for work viewing)
>
> --
> Jeff Squyres
> jsquyres(a)cisco.com
> For corporate legal information go to: http://www.cisco.com/web/
> about/doing_business/legal/cri/
>
> _______________________________________________
> mpiwg-fortran mailing list
> mpiwg-fortran(a)lists.mpi-forum.org
> https://lists.mpi-forum.org/mailman/listinfo/mpiwg-fortran
>
--
Jeff Hammond
jeff.science(a)gmail.com
http://jeffhammond.github.io/
OK, I voted. I’d seen this package before. I suspect that if someone was developing this today, it would look a lot different. Especially now that Fortran supports C-style byte-stream I/O and also provides user-defined I/O capabilities. The SQL interface could be useful, though.
Cheers,
Bill
On Dec 21, 2016, at 8:54 AM, Jeff Squyres (jsquyres) <jsquyres(a)cisco.com> wrote:
> Fortran people totally must vote:
>
> https://docs.google.com/forms/d/e/1FAIpQLSfkR0lXwzwc-p7AMGpGKUvjy8POT5X11QH…
>
> (This is safe for work viewing)
>
> --
> Jeff Squyres
> jsquyres(a)cisco.com
> For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
>
> _______________________________________________
> mpiwg-fortran mailing list
> mpiwg-fortran(a)lists.mpi-forum.org
> https://lists.mpi-forum.org/mailman/listinfo/mpiwg-fortran
Bill Long longb(a)cray.com
Fortran Technical Support & voice: 651-605-9024
Bioinformatics Software Development fax: 651-605-9142
Cray Inc./ Cray Plaza, Suite 210/ 380 Jackson St./ St. Paul, MN 55101
The list should be available again. It's possible that things might not work in your particular area yet if your DNS updates slowly.
> On Oct 3, 2016, at 9:43 AM, Bland, Wesley <wesley.bland(a)intel.com> wrote:
>
> After delaying the migration a bit to avoid interrupting the forum meeting and EuroMPI, we're ready to do the migration today. It's possible that there will be some brief outages between now and the end of the day while DNS records are updated and most likely any emails sent today could end up not getting archived correctly.
>
> Make sure you are using the correct address for this list in the future as any aliases that might have worked in the past will almost certainly not work in the future:
>
> mpiwg-co(a)lists.mpi-forum.org
>
> Thanks,
> Wesley
>
_______________________________________________
mpiwg-fortran mailing list
mpiwg-fortran(a)lists.mpi-forum.org
https://lists.mpi-forum.org/mailman/listinfo/mpiwg-fortran
After delaying the migration a bit to avoid interrupting the forum meeting and EuroMPI, we're ready to do the migration today. It's possible that there will be some brief outages between now and the end of the day while DNS records are updated and most likely any emails sent today could end up not getting archived correctly.
Make sure you are using the correct address for this list in the future as any aliases that might have worked in the past will almost certainly not work in the future:
mpiwg-co(a)lists.mpi-forum.org
Thanks,
Wesley
_______________________________________________
mpiwg-fortran mailing list
mpiwg-fortran(a)lists.mpi-forum.org
http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
TL;DR - The DNS records for the MPI Forum will be moving from Illinois to Google tonight<http://airmail.calendar/2016-09-06%2019:00:00%20CDT>. This should have user impact, but it’s possible that there will be a short outage depending on your local DNS caches. Other services will be migrating soon.
More Details - As part of the overall migration process that I referenced in an email about a month ago, we’re moving the DNS records out of the University of Illinois and up to the cloud (in this case, Google Domains). This should have no impact on your ability to view websites or send emails to these mailing lists, but it’s possible that as the new DNS information propagates to all of the caches around the world, there will be some brief outages. For now, nothing should change.
If everything goes well tonight<http://airmail.calendar/2016-09-06%2019:00:00%20CDT>, I hope to start migrating services next week (with the intention of having everything migrated before the 14th<http://airmail.calendar/2016-09-06%2012:00:00%20CDT> so we can make sure everything is stable for EuroMPI and the September MPI Forum meeting.
Here is the rough timeline:
Sometime this week - Move DNS records from UIUC to Google (hard to predict exactly when this happens)
This week - Prepare mailing lists (moving from Indiana to Argonne) and website (website preview available at https://mpi-forum.github.io/) for move.
Early next week - Move mailing lists and website to their new hosts
September 14th<http://airmail.calendar/2016-09-14%2012:00:00%20CDT> - Migration complete (anything not migrated will be postponed until after the EuroMPI/MPI Forum meeting)
If you have questions/concerns about the migration, new website, mailing lists, etc., please let me know.
Thanks,
Wesley
Jeff and Craig,
I'm also good with this, but technically, in my opinion,
the following changes are needed:
- Page 604, lines 19-20 of
https://github.com/mpi-forum/mpi-issues/files/221301/mpi-report-deprecate-m…
read
The following Fortran subroutines are deprecated;
the Fortran language storage_size() and c_sizeof()
intrinsic functions provide this functionality.
but should read (proposal)
The following Fortran subroutines are deprecated;
the Fortran language storage_size() and c_sizeof()
intrinsic functions provide similar functionality.
Whereas MPI_SIZEOF() and c_sizeof() provide the size
in bytes, the intrinsic storage_size() provides the
size in bits.
Otherwise it is a direct path to the hell when people
updating there deprecated source code.
- Page 631, lines 5-8 read
MPI_TYPE_MATCH_SIZE can be used to obtain a size-specific
type that matches a Fortran numeric intrinsic type by
first calling storage_size()in order to compute the
variable size, and then calling MPI_TYPE_MATCH_SIZE to find
a suitable datatype. In C, one can use the C function
sizeof(), instead of storage_size().
It is necessary to mention that storage_size() returns
bits and not bytes. It should be written in a way that a
Fortran reader Need not to read the C text and vice versa.
Proposal:
MPI_TYPE_MATCH_SIZE can be used to obtain a size-specific
type that matches a Fortran numeric intrinsic type by
first calling storage_size() in order to compute the
variable size in bits, deviding it by 8,
and then calling MPI_TYPE_MATCH_SIZE to find
a suitable datatype. In C, one can use the C function
sizeof(), which returns the size in bytes,
instead of storage_size() (which returns the size in bits).
- On page 18 in Table 2.1 the following mail should be added:
MPI_SIZEOF MPI-4.0 ____ storage_size() 5)
With footnote
5) Fortran intrinsic. It returs the size in bits instead of bytes.
- In the General index on page 721, I would recommend to add
the keyword "MPI_SIZEOF and storage_size()"
and all Locations of the both routines.
Best regards
Rolf
----- Original Message -----
> From: "Craig Rasmussen" <rasmus(a)cas.uoregon.edu>
> To: "MPI-WG Fortran working group" <mpiwg-fortran(a)lists.mpi-forum.org>
> Sent: Wednesday, April 20, 2016 1:52:18 AM
> Subject: Re: [MPIWG Fortran] Deprecate MPI_SIZEOF in MPI-4.0
> I'm good with this too.
>
> -craig
>
>
> On Fri, Apr 15, 2016 at 11:03 AM, Bill Long < longb(a)cray.com > wrote:
>
>
>
> On Apr 15, 2016, at 12:41 PM, Jeff Squyres (jsquyres) < jsquyres(a)cisco.com >
> wrote:
>
>> Re-sending because the reply-to on the original mail was incorrect (i.e., if you
>> replied and didn't hand-edit the reply address, it likely bounced).
>>
>>
>>> On Apr 15, 2016, at 11:57 AM, Jeff Squyres (jsquyres) < jsquyres(a)cisco.com >
>>> wrote:
>>>
>>> We brought this up forever ago (December 2014), and never progressed the issue
>>> (IIRC).
>>>
>>> It came up again today in a different context (in the Open MPI community). So I
>>> took the liberty of re-creating the issue in the Github MPI Forum system:
>>>
>>> https://github.com/mpi-forum/mpi-issues/issues/51
>>>
>>> We still want to move forward with this, right?
>
> I’m in favor.
>
> Cheers,
> Bill
>
>>>
>>> --
>>> Jeff Squyres
>>> jsquyres(a)cisco.com
>>> For corporate legal information go to:
>>> http://www.cisco.com/web/about/doing_business/legal/cri/
>>>
>>> _______________________________________________
>>> mpiwg-fortran mailing list
>>> mpiwg-fortran(a)mpi-forum.org
>>> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
>>
>>
>> --
>> Jeff Squyres
>> jsquyres(a)cisco.com
>> For corporate legal information go to:
>> http://www.cisco.com/web/about/doing_business/legal/cri/
>>
>> _______________________________________________
>> mpiwg-fortran mailing list
>> mpiwg-fortran(a)lists.mpi-forum.org
>> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
>
> Bill Long longb(a)cray.com
> Fortran Technical Support & voice: 651-605-9024
> Bioinformatics Software Development fax: 651-605-9142
> Cray Inc./ Cray Plaza, Suite 210/ 380 Jackson St./ St. Paul, MN 55101
>
>
> _______________________________________________
> mpiwg-fortran mailing list
> mpiwg-fortran(a)lists.mpi-forum.org
> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
>
>
> _______________________________________________
> mpiwg-fortran mailing list
> mpiwg-fortran(a)lists.mpi-forum.org
> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
--
Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner(a)hlrs.de
High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530
University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832
Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner
Nobelstr. 19, D-70550 Stuttgart, Germany . . . . (Office: Room 1.307)
I'm good with this too.
-craig
On Fri, Apr 15, 2016 at 11:03 AM, Bill Long <longb(a)cray.com> wrote:
>
> On Apr 15, 2016, at 12:41 PM, Jeff Squyres (jsquyres) <jsquyres(a)cisco.com>
> wrote:
>
> > Re-sending because the reply-to on the original mail was incorrect
> (i.e., if you replied and didn't hand-edit the reply address, it likely
> bounced).
> >
> >
> >> On Apr 15, 2016, at 11:57 AM, Jeff Squyres (jsquyres) <
> jsquyres(a)cisco.com> wrote:
> >>
> >> We brought this up forever ago (December 2014), and never progressed
> the issue (IIRC).
> >>
> >> It came up again today in a different context (in the Open MPI
> community). So I took the liberty of re-creating the issue in the Github
> MPI Forum system:
> >>
> >> https://github.com/mpi-forum/mpi-issues/issues/51
> >>
> >> We still want to move forward with this, right?
>
> I’m in favor.
>
> Cheers,
> Bill
>
> >>
> >> --
> >> Jeff Squyres
> >> jsquyres(a)cisco.com
> >> For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/
> >>
> >> _______________________________________________
> >> mpiwg-fortran mailing list
> >> mpiwg-fortran(a)mpi-forum.org
> >> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
> >
> >
> > --
> > Jeff Squyres
> > jsquyres(a)cisco.com
> > For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/
> >
> > _______________________________________________
> > mpiwg-fortran mailing list
> > mpiwg-fortran(a)lists.mpi-forum.org
> > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
>
> Bill Long
> longb(a)cray.com
> Fortran Technical Support & voice:
> 651-605-9024
> Bioinformatics Software Development fax: 651-605-9142
> Cray Inc./ Cray Plaza, Suite 210/ 380 Jackson St./ St. Paul, MN 55101
>
>
> _______________________________________________
> mpiwg-fortran mailing list
> mpiwg-fortran(a)lists.mpi-forum.org
> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
>
On Apr 15, 2016, at 12:41 PM, Jeff Squyres (jsquyres) <jsquyres(a)cisco.com> wrote:
> Re-sending because the reply-to on the original mail was incorrect (i.e., if you replied and didn't hand-edit the reply address, it likely bounced).
>
>
>> On Apr 15, 2016, at 11:57 AM, Jeff Squyres (jsquyres) <jsquyres(a)cisco.com> wrote:
>>
>> We brought this up forever ago (December 2014), and never progressed the issue (IIRC).
>>
>> It came up again today in a different context (in the Open MPI community). So I took the liberty of re-creating the issue in the Github MPI Forum system:
>>
>> https://github.com/mpi-forum/mpi-issues/issues/51
>>
>> We still want to move forward with this, right?
I’m in favor.
Cheers,
Bill
>>
>> --
>> Jeff Squyres
>> jsquyres(a)cisco.com
>> For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
>>
>> _______________________________________________
>> mpiwg-fortran mailing list
>> mpiwg-fortran(a)mpi-forum.org
>> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
>
>
> --
> Jeff Squyres
> jsquyres(a)cisco.com
> For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
>
> _______________________________________________
> mpiwg-fortran mailing list
> mpiwg-fortran(a)lists.mpi-forum.org
> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
Bill Long longb(a)cray.com
Fortran Technical Support & voice: 651-605-9024
Bioinformatics Software Development fax: 651-605-9142
Cray Inc./ Cray Plaza, Suite 210/ 380 Jackson St./ St. Paul, MN 55101
