public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/30835] ICE with -O2 -ftree-loop-linear
Date: Sat, 17 Feb 2007 20:24:00 -0000	[thread overview]
Message-ID: <20070217202442.5421.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30835-6642@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from steven at gcc dot gnu dot org  2007-02-17 20:24 -------
(gdb) run
Starting program: ./f951 -O2 -ftree-loop-linear t.f90
 xas_env_init
Analyzing compilation unit
Performing interprocedural optimizations
 <visibility> <early_local_cleanups> <inline> <static-var> <pure-const>
<type-escape-var>Assembling functions:
 xas_env_init
Program received signal SIGSEGV, Segmentation fault.
0x0000000000d17446 in can_convert_to_perfect_nest (loop=0x1147530)
    at ../../trunk/gcc/lambda-code.c:2363
2363                                    if (bb_for_stmt (arg_stmt)->loop_father
(gdb) bt 10
#0  0x0000000000d17446 in can_convert_to_perfect_nest (loop=0x1147530)
    at ../../trunk/gcc/lambda-code.c:2363
#1  0x0000000000d1272b in gcc_loopnest_to_lambda_loopnest (loop_nest=0x1147530,
    inductionvars=0x7ffffff106b8, invariants=0x7ffffff106b0) at
../../trunk/gcc/lambda-code.c:1475
#2  0x0000000000ce2944 in linear_transform_loops () at
../../trunk/gcc/tree-loop-linear.c:322
#3  0x0000000000902b26 in tree_linear_transform () at
../../trunk/gcc/tree-ssa-loop.c:217
#4  0x0000000000729274 in execute_one_pass (pass=0x1048420) at
../../trunk/gcc/passes.c:1055
#5  0x00000000007293be in execute_pass_list (pass=0x1048420) at
../../trunk/gcc/passes.c:1107
#6  0x00000000007293dc in execute_pass_list (pass=0x1048240) at
../../trunk/gcc/passes.c:1108
#7  0x00000000007293dc in execute_pass_list (pass=0x1047700) at
../../trunk/gcc/passes.c:1108
#8  0x0000000000852d84 in tree_rest_of_compilation (fndecl=0x2aaaab14d2a0)
    at ../../trunk/gcc/tree-optimize.c:412
#9  0x0000000000479d6b in gfc_expand_function (fndecl=0x2aaaab14d2a0)
    at ../../trunk/gcc/fortran/f95-lang.c:239
(More stack frames follow...)
(gdb)        


-- 

steven at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2007-02-17 20:24:42
               date|                            |


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


  reply	other threads:[~2007-02-17 20:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-17 16:15 [Bug middle-end/30835] New: " jv244 at cam dot ac dot uk
2007-02-17 20:24 ` steven at gcc dot gnu dot org [this message]
2007-03-11 22:31 ` [Bug middle-end/30835] " rakdver at gcc dot gnu dot org
2007-03-12 21:56 ` rakdver at gcc dot gnu dot org
2007-03-14 16:30 ` jv244 at cam dot ac dot uk
2007-03-15  8:47 ` burnus 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=20070217202442.5421.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).