public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/31197] [4.3/4.2 regression^2] TRANSPOSE/RESHAPE and strings
Date: Wed, 18 Apr 2007 09:54:00 -0000	[thread overview]
Message-ID: <20070418095417.17564.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31197-6642@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from fxcoudert at gcc dot gnu dot org  2007-04-18 10:54 -------
Hey, this has turned into an ICE on today's trunk. Cool, it's gonna be easier
to work on! :)

As I pointed out in http://gcc.gnu.org/ml/fortran/2007-04/msg00295.html, this
makes it a potential double regression, which is nasty.


Program received signal SIGSEGV, Segmentation fault.
0x000000000048048b in gfc_conv_function_call (se=0x7fbfffe750, sym=0xe372c0, 
    arg=0xe004f0, append_args=0x0)
    at /utmp/coudert/gfortran/trunk/gcc/fortran/trans-expr.c:2053
2053      need_interface_mapping = ((sym->ts.type == BT_CHARACTER
(gdb) where
#0  0x000000000048048b in gfc_conv_function_call (se=0x7fbfffe750, 
    sym=0xe372c0, arg=0xe004f0, append_args=0x0)
    at /utmp/coudert/gfortran/trunk/gcc/fortran/trans-expr.c:2053
#1  0x000000000048a685 in gfc_conv_intrinsic_funcall (se=0x7fbfffe750, 
    expr=0xe35fe0)
    at /utmp/coudert/gfortran/trunk/gcc/fortran/trans-intrinsic.c:1514
#2  0x000000000048c341 in gfc_conv_intrinsic_function (se=0x7fbfffe750, 
    expr=0xe35fe0)
    at /utmp/coudert/gfortran/trunk/gcc/fortran/trans-intrinsic.c:3945
#3  0x0000000000480ae7 in gfc_conv_function_expr (se=0x7fbfffe750,
expr=Variable "expr" is not available.
)
    at /utmp/coudert/gfortran/trunk/gcc/fortran/trans-expr.c:2698
#4  0x000000000046f449 in gfc_add_loop_ss_code (loop=0x7fbfffe920, 
    ss=0xe37110, subscript=0 '\0')
    at /utmp/coudert/gfortran/trunk/gcc/fortran/trans-array.c:1803
#5  0x000000000046fcb6 in gfc_conv_loop_setup (loop=0x7fbfffe920)
    at /utmp/coudert/gfortran/trunk/gcc/fortran/trans-array.c:3232
#6  0x000000000048d881 in gfc_trans_transfer (code=Variable "code" is not
available.
)
    at /utmp/coudert/gfortran/trunk/gcc/fortran/trans-io.c:1850
#7  0x0000000000467ae5 in gfc_trans_code (code=0xe2b9a0)
    at /utmp/coudert/gfortran/trunk/gcc/fortran/trans.c:605
#8  0x000000000048fa82 in build_dt (function=0x2a984c5540, code=0xe36cc0)
    at /utmp/coudert/gfortran/trunk/gcc/fortran/trans-io.c:1507
#9  0x0000000000467b09 in gfc_trans_code (code=0xe36cc0)
    at /utmp/coudert/gfortran/trunk/gcc/fortran/trans.c:581
#10 0x000000000047b437 in gfc_generate_function_code (ns=0xe2b1c0)
    at /utmp/coudert/gfortran/trunk/gcc/fortran/trans-decl.c:3181


-- 

fxcoudert at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fxcoudert at gcc dot gnu dot
                   |                            |org
           Severity|normal                      |major
           Keywords|                            |ice-on-valid-code
      Known to fail|                            |4.3.0 4.2.0
      Known to work|                            |4.1.2
   Last reconfirmed|2007-03-16 13:25:05         |2007-04-18 10:54:17
               date|                            |
            Summary|wrong code generated with   |[4.3/4.2 regression^2]
                   |TRANSPOSE/RESHAPE and       |TRANSPOSE/RESHAPE and
                   |strings                     |strings


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


  parent reply	other threads:[~2007-04-18  9:54 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-16 11:26 [Bug fortran/31197] New: wrong code generated with gfortran jv244 at cam dot ac dot uk
2007-03-16 13:25 ` [Bug fortran/31197] wrong code generated with TRANSPOSE/RESHAPE and strings burnus at gcc dot gnu dot org
2007-04-18  9:54 ` fxcoudert at gcc dot gnu dot org [this message]
2007-04-18 14:56 ` [Bug fortran/31197] [4.3/4.2 regression^2] " tobi at gcc dot gnu dot org
2007-04-18 18:30 ` tobi at gcc dot gnu dot org
2007-05-04 16:21 ` jvdelisle at gcc dot gnu dot org
2007-05-04 16:29 ` fxcoudert at gcc dot gnu dot org
2007-05-04 16:51 ` jvdelisle at gcc dot gnu dot org
2007-05-04 19:39 ` jvdelisle at gcc dot gnu dot org
2007-05-04 21:29 ` burnus at gcc dot gnu dot org
2007-05-15  6:48 ` elizabeth dot l dot yip at boeing dot com
2007-05-21 19:10 ` elizabeth dot l dot yip at boeing dot com
2007-06-11 12:53 ` pault at gcc dot gnu dot org
2007-06-30  9:16 ` [Bug fortran/31197] [4.2/4.4 regression] " pinskia at gcc dot gnu dot org
2007-07-03 18:33 ` [Bug fortran/31197] [4.2/4.3 " jv244 at cam dot ac dot uk
2007-07-03 18:36 ` tobi at gcc dot gnu dot org
2007-07-04  3:06 ` mmitchel at gcc dot gnu dot org
2007-07-04  8:50 ` pault at gcc dot gnu dot org
2007-07-04  9:09 ` jv244 at cam dot ac dot uk
2007-07-04  9:10 ` jv244 at cam dot ac dot uk
2007-07-04  9:27 ` pault at gcc dot gnu dot org
2007-07-04 10:05 ` jv244 at cam dot ac dot uk
2007-07-04 10:51 ` Tobias dot Schlueter at physik dot uni-muenchen dot de
2007-07-04 11:32 ` pault at gcc dot gnu dot org
2007-08-30 22:11 ` pault at gcc dot gnu dot org
2007-08-30 22:13 ` pault 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=20070418095417.17564.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: 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).