From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Mikael Morin <mikael.morin@sfr.fr>
Cc: Andre Vehreschild <vehre@gmx.de>,
GCC-Patches-ML <gcc-patches@gcc.gnu.org>,
GCC-Fortran-ML <fortran@gcc.gnu.org>,
Paul Richard Thomas <paul.richard.thomas@gmail.com>
Subject: Re: [RFC, Fortran, (pr66775)] Allocatable function result
Date: Fri, 10 Jul 2015 18:57:00 -0000 [thread overview]
Message-ID: <20150710185713.GA92724@troutmask.apl.washington.edu> (raw)
In-Reply-To: <559FF0DF.8080107@sfr.fr>
On Fri, Jul 10, 2015 at 06:20:47PM +0200, Mikael Morin wrote:
>
> I'm not completely convinced by the standard excerpts that have been
> quoted about this topic, as they don't have any explicit mention of
> allocatable variables/expressions.
I did not quote 12.3.3 about "characteristics of function results",
which mentions the allocatable attribute. But, that is not
necessarily relevant. The pieces I quoted explicitly states
"On completion of execution of the function, the value returned
is that of its function result. ... If the function result is
not a pointer, its value shall be defined by the function."
The function not only needs to allocate memory, it needs to
assign it a value. In the following, if i <= 0, the function
result is not defined.
module foo
contains
function bar(i)
integer, allocatable :: bar
integer, intent(in) :: i
if (i > 0) bar = i
end function bar
end module foo
program test
use foo
integer j
j = bar( 3); print *, j
j = bar(-3); print *, j
end if
end program test
Even if Andre developed a patch to allocate memory in
bar() for the i <= 0 case to prevent the segfault, the
function must return a value. What should that value be?
I suppose one could argue that gfortran should issue
a run-time error if it can detect the undefined function
result. But may lead to a run-time penalty.
--
Steve
next prev parent reply other threads:[~2015-07-10 18:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 10:25 Andre Vehreschild
2015-07-09 17:50 ` Steve Kargl
2015-07-09 18:59 ` Andre Vehreschild
2015-07-09 19:41 ` Steve Kargl
2015-07-10 9:44 ` Andre Vehreschild
2015-07-10 13:41 ` Steve Kargl
2015-07-10 16:20 ` Mikael Morin
2015-07-10 16:44 ` Andre Vehreschild
2015-07-10 18:57 ` Steve Kargl [this message]
2015-07-11 10:37 ` Andre Vehreschild
2015-07-11 11:06 ` Mikael Morin
2015-07-11 11:58 ` Dan Nagle
2015-07-13 17:27 ` Mike Stump
2015-07-11 10:54 ` Mikael Morin
2015-07-11 10:58 ` Andre Vehreschild
2015-07-11 15:37 ` Steve Kargl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150710185713.GA92724@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=mikael.morin@sfr.fr \
--cc=paul.richard.thomas@gmail.com \
--cc=vehre@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).