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/46978] [4.6 Regression] TRANSPOSE with RESHAPE and ALLOCATE: Segfault
Date: Mon, 20 Dec 2010 23:25:00 -0000	[thread overview]
Message-ID: <bug-46978-4-jFMddjUIOL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46978-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46978

--- Comment #7 from Mikael Morin <mikael at gcc dot gnu.org> 2010-12-20 23:24:54 UTC ---
This seems to fix it, though I find it somewhat suspicious. 

Index: trans-array.c
===================================================================
--- trans-array.c    (révision 164205)
+++ trans-array.c    (copie de travail)
@@ -851,8 +851,8 @@ gfc_trans_create_temp_array (stmtblock_t * pre, st
          of the descriptor fields.  */
       tmp = fold_build2_loc (input_location,
         MINUS_EXPR, gfc_array_index_type,
-        gfc_conv_descriptor_ubound_get (desc, gfc_rank_cst[n]),
-        gfc_conv_descriptor_lbound_get (desc, gfc_rank_cst[n]));
+        gfc_conv_descriptor_ubound_get (desc, gfc_rank_cst[dim]),
+        gfc_conv_descriptor_lbound_get (desc, gfc_rank_cst[dim]));
       loop->to[n] = tmp;
       continue;
     }


I remember making this change back and forth, and indeed, it reverts part of
revision 164112, but the regression is at revision 164205. Strange.


  parent reply	other threads:[~2010-12-20 23:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-16  9:10 [Bug fortran/46978] New: TRANSPOSE corrupts structure and memory m.a.hulsen at tue dot nl
2010-12-16 10:20 ` [Bug fortran/46978] " dominiq at lps dot ens.fr
2010-12-16 10:33 ` m.a.hulsen at tue dot nl
2010-12-16 11:21 ` [Bug fortran/46978] [4.6 Regression] " burnus at gcc dot gnu.org
2010-12-16 14:49 ` burnus at gcc dot gnu.org
2010-12-16 15:27 ` jakub at gcc dot gnu.org
2010-12-16 21:32 ` [Bug fortran/46978] [4.6 Regression] TRANSPOSE with RESHAPE and ALLOCATE: Segfault burnus at gcc dot gnu.org
2010-12-17 19:28 ` mikael at gcc dot gnu.org
2010-12-19 15:47 ` mikael at gcc dot gnu.org
2010-12-20 23:25 ` mikael at gcc dot gnu.org [this message]
2010-12-20 23:29 ` mikael at gcc dot gnu.org
2010-12-22 12:37 ` mikael at gcc dot gnu.org
2010-12-23  9:13 ` m.a.hulsen at tue dot nl
2010-12-23 13:36 ` mikael at gcc dot gnu.org
2010-12-23 13:39 ` mikael at gcc dot gnu.org
2010-12-23 13:43 ` 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-46978-4-jFMddjUIOL@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: 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).