public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "antoine.balestrat at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/56426] New: Segmentation fault in find_var_scev_info, at tree-scalar-evolution.c:358
Date: Fri, 22 Feb 2013 14:52:00 -0000	[thread overview]
Message-ID: <bug-56426-4@http.gcc.gnu.org/bugzilla/> (raw)


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

             Bug #: 56426
           Summary: Segmentation fault in find_var_scev_info, at
                    tree-scalar-evolution.c:358
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: antoine.balestrat@gmail.com


Using GCC 4.8.0 as of 20130222 :

$ cat scev.c
int a, *c;

void f(void)
{
    int b = 0;

    for(a = 0;; a++)
        if(--b)
        {
            if(a)
lbl:
                a++;

            c = &b;
            goto lbl;
        }
}

$ xgcc -w -O2 scev.c
scev.c: In function ‘f’:
scev.c:3:6: internal compiler error: Segmentation fault
 void f(void)
      ^
0x8f89ef crash_signal
    ../../srcdir/gcc/toplev.c:332
0xe1228f htab_find_slot
    ../../srcdir/libiberty/hashtab.c:712
0x98caf5 find_var_scev_info
    ../../srcdir/gcc/tree-scalar-evolution.c:358
0x98f999 get_scalar_evolution
    ../../srcdir/gcc/tree-scalar-evolution.c:559
0x98f999 analyze_scalar_evolution(loop*, tree_node*)
    ../../srcdir/gcc/tree-scalar-evolution.c:1963
0xa00287 infer_loop_bounds_from_signedness
    ../../srcdir/gcc/tree-ssa-loop-niter.c:2887
0xa00287 infer_loop_bounds_from_undefined
    ../../srcdir/gcc/tree-ssa-loop-niter.c:2944
0xa00287 estimate_numbers_of_iterations_loop
    ../../srcdir/gcc/tree-ssa-loop-niter.c:3340
0xa00287 estimate_numbers_of_iterations_loop(loop*)
    ../../srcdir/gcc/tree-ssa-loop-niter.c:3302
0xa015e4 estimate_numbers_of_iterations()
    ../../srcdir/gcc/tree-ssa-loop-niter.c:3534
0xa01aa7 tree_ssa_loop_bounds
    ../../srcdir/gcc/tree-ssa-loop.c:432
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.


             reply	other threads:[~2013-02-22 14:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-22 14:52 antoine.balestrat at gmail dot com [this message]
2013-02-22 15:50 ` [Bug tree-optimization/56426] [4.8 Regression] " mpolacek at gcc dot gnu.org
2013-02-25  8:45 ` rguenth at gcc dot gnu.org
2013-02-25 10:58 ` mpolacek at gcc dot gnu.org
2013-02-25 12:15 ` mpolacek at gcc dot gnu.org
2013-02-25 12:50 ` rguenth at gcc dot gnu.org
2013-02-25 14:07 ` mpolacek at gcc dot gnu.org
2013-02-26 11:07 ` mpolacek at gcc dot gnu.org
2013-02-26 11:08 ` mpolacek 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-56426-4@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).