public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/41137] inefficient zeroing of an array Date: Fri, 29 Mar 2013 22:39:00 -0000 [thread overview] Message-ID: <bug-41137-4-1woEVWDmj3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-41137-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41137 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |burnus at gcc dot gnu.org --- Comment #16 from Tobias Burnus <burnus at gcc dot gnu.org> 2013-03-29 22:38:58 UTC --- Possible off-topic remark - or hitting right on the nail: Looking at a(:,:,:,:)=0.0 and a(5:) = 0.0 I wonder whether it couldn't be handled via RANGE_REF, e.g. RANGE_REF(a,5,...) = { }; should work if I am not mistaken. Currently, we only do "a = 0.0" -> "a = {};". See ARRAY_RANGE_REF in trans-expr.c's class_array_data_assign (gfc_index_zero_node is the offset) for the usage; see also GCC internal manual and Ada.
next prev parent reply other threads:[~2013-03-29 22:39 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-41137-4@http.gcc.gnu.org/bugzilla/> 2013-03-29 9:47 ` Joost.VandeVondele at mat dot ethz.ch 2013-03-29 22:19 ` tkoenig at gcc dot gnu.org 2013-03-29 22:39 ` burnus at gcc dot gnu.org [this message] 2014-05-01 12:16 ` dominiq at lps dot ens.fr 2014-05-01 12:35 ` Joost.VandeVondele at mat dot ethz.ch 2014-05-01 17:00 ` tkoenig at gcc dot gnu.org 2021-12-26 5:51 ` [Bug tree-optimization/41137] " pinskia at gcc dot gnu.org 2021-12-26 5:51 ` pinskia at gcc dot gnu.org 2009-08-21 6:15 [Bug fortran/41137] New: " jv244 at cam dot ac dot uk 2009-08-21 7:02 ` [Bug fortran/41137] " jv244 at cam dot ac dot uk 2009-08-21 7:40 ` dfranke at gcc dot gnu dot org 2009-08-21 8:29 ` jv244 at cam dot ac dot uk 2009-08-24 20:06 ` jv244 at cam dot ac dot uk 2009-11-01 16:21 ` tkoenig at gcc dot gnu dot org 2009-11-01 17:36 ` tkoenig at gcc dot gnu dot org 2010-05-07 21:02 ` dfranke at gcc dot gnu dot org 2010-06-21 15:02 ` burnus at gcc dot gnu dot org 2010-06-21 15:22 ` burnus at gcc dot gnu dot org 2010-06-21 15:49 ` jv244 at cam dot ac dot uk 2010-06-21 17:00 ` burnus at gcc dot gnu dot org 2010-06-21 17:44 ` jakub at gcc dot gnu dot org 2010-06-22 14:42 ` burnus at gcc dot gnu dot org 2010-06-22 15:25 ` jakub at gcc dot gnu dot 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-41137-4-1woEVWDmj3@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).