public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/32461] [4.3 Regression] Segmentation fault in build_classic_dist_vector_1() at tree-data-ref.c:2700
Date: Fri, 22 Jun 2007 18:29:00 -0000	[thread overview]
Message-ID: <20070622182905.14479.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32461-13856@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from ubizjak at gmail dot com  2007-06-22 18:29 -------
The testcase:

--cut here--
typedef struct
{
  unsigned char exp[256];
}
expbap_t;

void
a52_bit_allocate (expbap_t * expbap)
{
  int i;
  unsigned char *exp;
  exp = expbap->exp;

  int lowcomp;
  do
    {
      if (exp[i + 1] == exp[i] - 2)
        lowcomp = 384;
      else if (lowcomp && (exp[i + 1] > exp[i]))
        lowcomp -= 64;
      i++;
    }
  while ((i < 3) || ((i < 7) && (exp[i] > exp[i - 1])));
}
--cut here--

gcc -O3 -m32:

#0  build_classic_dist_vector_1 (ddr=0xf84eb0, ddr_a=0xf84460, ddr_b=0xf84f50, 
    dist_v=0x2aaaae0aa260, init_b=0x7ffffed24dd7
"\001&#65533;\206&#65533;&#65533;&#65533;*", 
    index_carry=0x7ffffed24dd0) at ../../gcc-svn/trunk/gcc/tree-data-ref.c:2700
#1  0x00000000006c2175 in subscript_dependence_tester (ddr=0xf84eb0, 
    loop_nest=0x2aaaadff86e0) at ../../gcc-svn/trunk/gcc/tree-data-ref.c:2998
#2  0x00000000006c3068 in compute_all_dependences (datarefs=0xf781d0, 
    dependence_relations=0x7ffffed25108, loop_nest=0xf73920, 
    compute_self_and_rr=1 '\001')
    at ../../gcc-svn/trunk/gcc/tree-data-ref.c:3805
#3  0x00000000006c3ebd in compute_data_dependences_for_loop (
    loop=0x2aaaadff86e0, compute_self_and_read_read_dependences=22 '\026', 
    datarefs=0x7ffffed25110, dependence_relations=0x7ffffed25108)
    at ../../gcc-svn/trunk/gcc/tree-data-ref.c:4117
#4  0x0000000000a1d992 in tree_predictive_commoning_loop (loop=0x2aaaadff86e0)
    at ../../gcc-svn/trunk/gcc/tree-predcom.c:2488
#5  0x0000000000a1ee85 in tree_predictive_commoning ()
    at ../../gcc-svn/trunk/gcc/tree-predcom.c:2596
#6  0x0000000000766ee7 in run_tree_predictive_commoning ()
    at ../../gcc-svn/trunk/gcc/tree-ssa-loop.c:184

(gdb) list
2695      for (i = 0; i < DDR_NUM_SUBSCRIPTS (ddr); i++)
2696        {
2697          tree access_fn_a, access_fn_b;
2698          struct subscript *subscript = DDR_SUBSCRIPT (ddr, i);
2699
2700 >>>>     if (chrec_contains_undetermined (SUB_DISTANCE (subscript)))
2701            {
2702              non_affine_dependence_relation (ddr);
2703              return false;
2704            }


-- 

ubizjak at gmail dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
          Component|regression                  |tree-optimization
     Ever Confirmed|0                           |1
   GCC host triplet|                            |i686-pc-linux-gnu
 GCC target triplet|                            |i686-pc-linux-gnu
   Last reconfirmed|0000-00-00 00:00:00         |2007-06-22 18:29:05
               date|                            |
            Summary|[4.3 Regression] internal   |[4.3 Regression]
                   |compiler error: Segmentation|Segmentation fault in
                   |fault                       |build_classic_dist_vector_1(
                   |                            |) at tree-data-ref.c:2700


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


  parent reply	other threads:[~2007-06-22 18:29 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-22 16:00 [Bug regression/32461] New: [4.3 Regression] internal compiler error: Segmentation fault jojelino at gmail dot com
2007-06-22 16:01 ` [Bug regression/32461] " jojelino at gmail dot com
2007-06-22 16:06 ` jojelino at gmail dot com
2007-06-22 18:29 ` ubizjak at gmail dot com [this message]
2007-06-23 10:21 ` [Bug tree-optimization/32461] [4.3 Regression] Segmentation fault in build_classic_dist_vector_1() at tree-data-ref.c:2700 spop at gcc dot gnu dot org
2007-06-23 10:28 ` ubizjak at gmail dot com
2007-06-23 11:05 ` spop at gcc dot gnu dot org
2007-06-23 18:11 ` spop at gcc dot gnu dot org
2007-06-23 18:37 ` richard dot guenther at gmail dot com
2007-06-23 19:24 ` richard dot guenther at gmail dot com
2007-06-24  3:53 ` pinskia at gcc dot gnu dot org
2007-06-24  6:48 ` spop at gcc dot gnu dot org
2007-06-24  7:55 ` sebpop at gmail dot com
2007-06-24 10:11 ` sebpop at gmail dot com
2007-06-24 10:26 ` ebotcazou at libertysurf dot fr
2007-06-24 10:27 ` pinskia at gmail dot com
2007-06-24 10:34 ` pinskia at gmail dot com
2007-06-24 10:46 ` ebotcazou at libertysurf dot fr
2007-06-24 11:40 ` richard dot guenther at gmail dot com
2007-06-24 12:50 ` sebpop at gmail dot com
2007-06-24 12:59 ` richard dot guenther at gmail dot com
2007-06-24 13:05 ` rask at sygehus dot dk
2007-06-24 13:35 ` schwab at suse dot de
2007-06-24 13:38 ` sebpop at gmail dot com
2007-06-24 19:19 ` sebpop at gmail dot com
2007-06-24 19:53 ` richard dot guenther at gmail dot com
2007-06-24 20:59 ` spop at gcc dot gnu dot org
2007-06-24 21:01 ` spop at gcc dot gnu dot org
2007-06-24 21:05 ` spop 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=20070622182905.14479.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).