public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/22516] [4.1 Regression] Segfault with ivopts at -O
Date: Sun, 17 Jul 2005 09:51:00 -0000	[thread overview]
Message-ID: <20050717080953.24912.qmail@sourceware.org> (raw)
In-Reply-To: <20050716215716.22516.falk@debian.org>


------- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-17 08:09 -------
Confirmed, backtrace:
#0  0x0010c034 in is_gimple_variable (t=0x0) at ../../gcc/tree-gimple.c:239
#1  0x0010c70c in is_gimple_val (t=0x0) at ../../gcc/tree-gimple.c:366
#2  0x0012bd94 in force_gimple_operand (expr=0x0, stmts=0xbffff528, simple=0 '\0', 
var=0x174d840) at ../../gcc/gimplify.c:4845
#3  0x001f1334 in rewrite_use_nonlinear_expr (data=0xbffff6f0, use=0x2105550, cand=0x2105830) 
at ../../gcc/tree-ssa-loop-ivopts.c:5365
#4  0x001f2dc8 in rewrite_use (data=0xbffff6f0, use=0x2105550, cand=0x2105830) at ../../gcc/tree-
ssa-loop-ivopts.c:5729
#5  0x001f2ed8 in rewrite_uses (data=0xbffff6f0) at ../../gcc/tree-ssa-loop-ivopts.c:5765
#6  0x001f3750 in tree_ssa_iv_optimize_loop (data=0xbffff6f0, loop=0x2105230) at ../../gcc/tree-
ssa-loop-ivopts.c:5941
#7  0x001f3858 in tree_ssa_iv_optimize (loops=0x21043a0) at ../../gcc/tree-ssa-loop-ivopts.c:5978
#8  0x001a3bf0 in tree_ssa_loop_ivopts () at ../../gcc/tree-ssa-loop.c:416
#9  0x005ba828 in execute_one_pass (pass=0x80cc8c) at ../../gcc/passes.c:778
#10 0x005ba948 in execute_pass_list (pass=0x80cc8c) at ../../gcc/passes.c:810
#11 0x005ba970 in execute_pass_list (pass=0x80ca50) at ../../gcc/passes.c:811
#12 0x005ba970 in execute_pass_list (pass=0x80c498) at ../../gcc/passes.c:811
#13 0x0010aaa0 in tree_rest_of_compilation (fndecl=0x174e780) at ../../gcc/tree-optimize.c:420

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rakdver at gcc dot gnu dot
                   |                            |org
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|                            |1
  GCC build triplet|alphaev68-unknown-linux-gnu |
   GCC host triplet|alphaev68-unknown-linux-gnu |
 GCC target triplet|alphaev68-unknown-linux-gnu |alphaev68-*-linux-gnu
   Last reconfirmed|0000-00-00 00:00:00         |2005-07-17 08:09:53
               date|                            |
            Summary|Segfault with ivopts at -O  |[4.1 Regression] Segfault
                   |                            |with ivopts at -O
   Target Milestone|---                         |4.1.0
            Version|4.0.2                       |4.1.0


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


  reply	other threads:[~2005-07-17  8:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-17  0:28 [Bug tree-optimization/22516] New: " falk at debian dot org
2005-07-17  9:51 ` pinskia at gcc dot gnu dot org [this message]
2005-07-18  9:46 ` [Bug tree-optimization/22516] [4.1 Regression] " rakdver at gcc dot gnu dot org
2005-09-09  1:01 ` janis at gcc dot gnu dot org
2005-09-10 13:04 ` belyshev at depni dot sinp dot msu dot ru

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=20050717080953.24912.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).