<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><span style="-webkit-text-size-adjust: auto;">Maybe GCC docs are wrong?</span></div><div><span style="-webkit-text-size-adjust: auto;"><br></span></div><div><span style="-webkit-text-size-adjust: auto;"><a href="http://gcc.gnu.org/onlinedocs/gfortran/STORAGE_005fSIZE.html">http://gcc.gnu.org/onlinedocs/gfortran/STORAGE_005fSIZE.html</a></span></div><div><span style="-webkit-text-size-adjust: auto;"><br></span></div><div><h3 class="section"><font size="3"><span style="background-color: rgba(255, 255, 255, 0);">8.238 <code>STORAGE_SIZE</code> — Storage size in bits</span></font></h3><p><font color="#000000"><span style="background-color: rgba(255, 255, 255, 0);"><a name="index-STORAGE_005fSIZE-1083"></a><a name="index-storage-size-1084"></a></span></font></p><dl><dt><span style="background-color: rgba(255, 255, 255, 0);"><em>Description</em>:</span></dt><dd><span style="background-color: rgba(255, 255, 255, 0);">Returns the storage size of argument <var>A</var> in bits. <br></span></dd><dt><span style="background-color: rgba(255, 255, 255, 0);"><em>Standard</em>:</span></dt><dd><span style="background-color: rgba(255, 255, 255, 0);">Fortran 2008 and later <br></span></dd><dt><span style="background-color: rgba(255, 255, 255, 0);"><em>Class</em>:</span></dt><dd><span style="background-color: rgba(255, 255, 255, 0);">Inquiry function <br></span></dd><dt><span style="background-color: rgba(255, 255, 255, 0);"><em>Syntax</em>:</span></dt><dd><font face="UICTFontTextStyleBody"><span style="background-color: rgba(255, 255, 255, 0);"><code>RESULT = STORAGE_SIZE(A [, KIND])</code> <br></span></font></dd><dt><span style="background-color: rgba(255, 255, 255, 0);"><em>Arguments</em>:</span></dt><dd><p></p><table summary=""><tbody><tr align="left"><td valign="top" width="15%"><var style="background-color: rgba(255, 255, 255, 0);">A</var></td><td valign="top" width="70%"><span style="background-color: rgba(255, 255, 255, 0);">Shall be a scalar or array of any type. <br></span></td></tr><tr align="left"><td valign="top" width="15%"><var style="background-color: rgba(255, 255, 255, 0);">KIND</var></td><td valign="top" width="70%"><span style="background-color: rgba(255, 255, 255, 0);">(Optional) shall be a scalar integer constant expression. <br></span></td></tr></tbody></table><span style="background-color: rgba(255, 255, 255, 0);"><br></span><p></p></dd><dt><span style="background-color: rgba(255, 255, 255, 0);"><em>Return Value</em>:</span></dt><dd><span style="background-color: rgba(255, 255, 255, 0);">The result is a scalar integer with the kind type parameter specified by KIND (or default integer type if KIND is missing). The result value is the size expressed in bits for an element of an array that has the dynamic type and type parameters of A. <br></span></dd><dt><span style="background-color: rgba(255, 255, 255, 0);"><em>See also</em>:</span></dt><dd><font color="#000000"><span style="background-color: rgba(255, 255, 255, 0);"><a href="http://gcc.gnu.org/onlinedocs/gfortran/C_005fSIZEOF.html#C_005fSIZEOF">C_SIZEOF</a>, <a href="http://gcc.gnu.org/onlinedocs/gfortran/SIZEOF.html#SIZEOF">SIZEOF</a></span></font></dd></dl><br><span style="-webkit-text-size-adjust: auto;">Sent from my iPhone</span></div><div style="-webkit-text-size-adjust: auto;"><br>On Jun 6, 2014, at 7:16 AM, "Jeff Squyres (jsquyres)" <<a href="mailto:jsquyres@cisco.com">jsquyres@cisco.com</a>> wrote:<br><br></div><blockquote type="cite" style="-webkit-text-size-adjust: auto;"><div><span>I'm still not sure why you're associating MPI_SIZEOF, F08, and storage_size together...?</span><br><span></span><br><span>According to earlier in the thread, storage_size has been around since F90. I.e., 20+ years. </span><br><span></span><br><span>Bill also mentioned that even though some compilers don't yet have it, a) it's easy to implement, and b) giving 2+ years warning to compilers that MPI intends to deprecate MPI_SIZEOF might well give compilers the nudge they need to go implement it.</span><br><span></span><br><span></span><br><span></span><br><span></span><br><span>On Jun 6, 2014, at 9:00 AM, Jeff Hammond <<a href="mailto:jeff.science@gmail.com">jeff.science@gmail.com</a>> wrote:</span><br><span></span><br><blockquote type="cite"><span>The majority of Fortran users in HPC are ignorant of F08 (beyond trivial notions, eg existence) and will still be by the time of MPI-4. I think deprecating this function must be coincident with deprecating the pre-F08 bindings since it is ootebtionskly required for pre-F08 MPI usage. </span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>If we are serious about forcing everyone to use F08 (which I think is a terrible idea), then let's at least do it consistently.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Jeff</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Sent from my iPhone</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>On Jun 6, 2014, at 5:15 AM, Bill Long <<a href="mailto:longb@cray.com">longb@cray.com</a>> wrote:</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>On Jun 6, 2014, at 6:31 AM, Jeff Squyres (jsquyres) <<a href="mailto:jsquyres@cisco.com">jsquyres@cisco.com</a>> wrote:</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>Would it still be ok to deprecate MPI_SIZEOF in MPI-4 (which is at least ~2 years away)? We don't have to have any plan for removing it.</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>I think that would be reasonable. In two years time more vendors will have implemented storage_size. And if it were well known that MPI wants people to migrate to this function, vendors would be motivated to add support sooner. The function itself is pretty trivial to implement as inline code by the compiler. It’s just a matter of vendor priorities.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Cheers,</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Bill</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Bill Long <a href="mailto:longb@cray.com">longb@cray.com</a></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Fortran Technical Suport & voice: 651-605-9024</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Bioinformatics Software Development fax: 651-605-9142</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Cray Inc./ Cray Plaza, Suite 210/ 380 Jackson St./ St. Paul, MN 55101</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>_______________________________________________</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>mpiwg-fortran mailing list</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span><a href="mailto:mpiwg-fortran@lists.mpi-forum.org">mpiwg-fortran@lists.mpi-forum.org</a></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span><a href="http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran">http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran</a></span><br></blockquote></blockquote><blockquote type="cite"><span>_______________________________________________</span><br></blockquote><blockquote type="cite"><span>mpiwg-fortran mailing list</span><br></blockquote><blockquote type="cite"><span><a href="mailto:mpiwg-fortran@lists.mpi-forum.org">mpiwg-fortran@lists.mpi-forum.org</a></span><br></blockquote><blockquote type="cite"><span><a href="http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran">http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran</a></span><br></blockquote><span></span><br><span></span><br><span>-- </span><br><span>Jeff Squyres</span><br><span><a href="mailto:jsquyres@cisco.com">jsquyres@cisco.com</a></span><br><span>For corporate legal information go to: <a href="http://www.cisco.com/web/about/doing_business/legal/cri/">http://www.cisco.com/web/about/doing_business/legal/cri/</a></span><br><span></span><br><span>_______________________________________________</span><br><span>mpiwg-fortran mailing list</span><br><span><a href="mailto:mpiwg-fortran@lists.mpi-forum.org">mpiwg-fortran@lists.mpi-forum.org</a></span><br><span><a href="http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran">http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran</a></span><br></div></blockquote></body></html>