public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mikael at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/64952] Missing temporary in assignment from elemental function Date: Fri, 06 Feb 2015 11:19:00 -0000 [thread overview] Message-ID: <bug-64952-4-XgxF8LclIG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64952-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64952 Mikael Morin <mikael at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mikael at gcc dot gnu.org --- Comment #2 from Mikael Morin <mikael at gcc dot gnu.org> --- (In reply to Paul Thomas from comment #0) > Fortunately, it only affects contained functions so that we do not have to > carry it across when using modules. > Don't we have to? Wouldn't it be the same if ARRAY and FRED were use-associated symbols, or if FRED was accessing ARRAY through use-association instead of host-association? (In reply to Tobias Burnus from comment #1) > On the other hand, it would be probably > faster to do: > tmp = pure_function() > array = elemental(array) * tmp > which also avoids this problem. As far as I know, the scalarizer does this already (in both cases where pure_function is scalar and non-scalar). By the way, a temporary is also necessary for array = Fred(index, other_array) that is, array need not be as argument to Fred.
next prev parent reply other threads:[~2015-02-06 11:19 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-05 19:22 [Bug fortran/64952] New: " pault at gcc dot gnu.org 2015-02-05 19:59 ` [Bug fortran/64952] " burnus at gcc dot gnu.org 2015-02-06 11:19 ` mikael at gcc dot gnu.org [this message] 2015-02-07 20:00 ` pault at gcc dot gnu.org 2015-02-08 13:00 ` mikael at gcc dot gnu.org 2015-03-23 8:27 ` mikael at gcc dot gnu.org 2015-03-23 9:35 ` paul.richard.thomas at gmail dot com 2015-03-23 12:28 ` mikael at gcc dot gnu.org 2015-03-24 10:02 ` ktkachov at gcc dot gnu.org 2015-03-24 10:16 ` dominiq at lps dot ens.fr 2015-03-24 10:52 ` mikael at gcc dot gnu.org 2015-03-25 11:10 ` mikael at gcc dot gnu.org 2015-03-26 13:03 ` mikael at gcc dot gnu.org
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=bug-64952-4-XgxF8LclIG@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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: linkBe 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).