public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pault at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/31610] ICE with transfer, merge in gfc_conv_expr_descriptor Date: Tue, 29 May 2007 13:39:00 -0000 [thread overview] Message-ID: <20070529133910.12390.qmail@sourceware.org> (raw) In-Reply-To: <bug-31610-6528@http.gcc.gnu.org/bugzilla/> ------- Comment #7 from pault at gcc dot gnu dot org 2007-05-29 13:39 ------- (In reply to comment #4) > I misunderstood something slightly in that last comment; MERGE is elemental, so > the conforming I mentioned doesn't matter. Also, my guess that fixing the > transfer("A", "x", 20) problem would fix the whole thing proved to be > incorrect. See comment #6. > So, even once the first bit is fixed, if we change the code to be legitimate, > as follows, then it still has an error: > character(len=20) :: string > logical :: a(20) > write(*,*) transfer (merge (transfer("A", "x", 20), "b", a), string ) > end It also fails with a character(len = 1) array of size 20. > Specifically, we ICE by failing the "gcc_assert (integer_zerop (loop -> > from[n]))" at line 593 of trans-array.c, when doing gfc_conv... stuff to the > arguments of the outer transfer function. > I'm having a bear of a time tracking down why this is happening. The problem > is that we're generating a temporary, so loop->temp_dim is 1 (as set in > gfc_trans_constant_array_constructor, line 1576). However, the loop seems to > be picking up dimensions from the result of the inner transfer function > somehow. Walking through the ss list for the loop gives a GFC_SS_CONSTRUCTOR, > a GFC_SS_SCALAR, and a GFC_SS_SECTION, and the GFC_SS_SECTION causes the > info->start[0] and info->end[0] values to be set (to 1 and 20, respectively) in > gfc_conv_ss_startstride, which then propagate to the from[0] and to[0] values > for the loop. > I can't seem to duplicate this with any other set of functions. It's only > happening with characters, not integers, and if I break up the expression or > substitute other things for transfer and merge, it doesn't replicate this > behavior. > Help? I'll have a think about this tonight. I NEVER find debugging the scalarizer easy; not in small part because I have to re-understand it every time I go near it. Paul -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31610
next prev parent reply other threads:[~2007-05-29 13:39 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-04-17 16:37 [Bug fortran/31610] New: " pinskia at gcc dot gnu dot org 2007-04-18 6:03 ` [Bug fortran/31610] " fxcoudert at gcc dot gnu dot org 2007-04-19 19:47 ` pault at gcc dot gnu dot org 2007-05-28 21:09 ` brooks at gcc dot gnu dot org 2007-05-29 5:59 ` brooks at gcc dot gnu dot org 2007-05-29 6:45 ` patchapp at dberlin dot org 2007-05-29 13:17 ` pault at gcc dot gnu dot org 2007-05-29 13:39 ` pault at gcc dot gnu dot org [this message] 2007-05-29 14:05 ` burnus at gcc dot gnu dot org 2007-05-29 14:25 ` dominiq at lps dot ens dot fr 2007-09-17 17:39 ` burnus at gcc dot gnu dot org 2007-11-12 0:19 ` fxcoudert at gcc dot gnu dot org 2007-11-22 9:09 ` fxcoudert at gcc dot gnu dot org 2007-12-08 17:16 ` jvdelisle at gcc dot gnu dot org 2008-01-25 20:23 ` [Bug fortran/31610] [4.3 Regression] " rguenth at gcc dot gnu dot org 2008-01-26 5:12 ` jvdelisle at gcc dot gnu dot org 2008-01-26 5:44 ` jvdelisle at gcc dot gnu dot org 2008-01-26 11:59 ` pault at gcc dot gnu dot org 2008-01-26 16:23 ` dominiq at lps dot ens dot fr 2008-01-26 17:19 ` jvdelisle at gcc dot gnu dot org 2008-01-26 19:10 ` jvdelisle at gcc dot gnu dot org 2008-01-26 19:14 ` jvdelisle at gcc dot gnu dot org 2008-01-26 19:24 ` [Bug fortran/31610] " jvdelisle at gcc dot gnu dot org 2008-03-15 0:41 ` jsm28 at gcc dot gnu dot org 2008-06-06 14:58 ` rguenth at gcc dot gnu dot org 2008-07-04 19:47 ` jsm28 at gcc dot gnu dot org 2008-11-15 15:21 ` pault at gcc dot gnu dot org 2008-11-15 18:43 ` burnus at gcc dot gnu dot org 2009-01-05 20:10 ` mikael 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=20070529133910.12390.qmail@sourceware.org \ --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).