public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: dominiq@lps.ens.fr (Dominique Dhumieres)
To: gcc-patches@gcc.gnu.org
Cc: tobias@grosser.es, gareevroman@gmail.com
Subject: Re: [GSoC] generation of Gimple loops with empty bodies
Date: Sat, 12 Jul 2014 10:13:00 -0000	[thread overview]
Message-ID: <20140712101339.BF8C3105@mailhost.lps.ens.fr> (raw)

On x86_64-apple-darwin13, the test gcc.dg/graphite/isl-codegen-loop-dumping.c
gives an ICE with -m32 after r212455. The backtrace is

* thread #1: tid = 0xdac306, 0x0000000100523c52 cc1`fold_binary_loc(loc=0, code=MINUS_EXPR, type=0x0000000000000000, op0=0x0000000142c09bd0, op1=0x0000000142c1b048) + 6402 at fold-const.c:10813, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x0)
    frame #0: 0x0000000100523c52 cc1`fold_binary_loc(loc=0, code=MINUS_EXPR, type=0x0000000000000000, op0=0x0000000142c09bd0, op1=0x0000000142c1b048) + 6402 at fold-const.c:10813
   10810	      if (TREE_CODE (type) != COMPLEX_TYPE
   10811		  && TREE_CODE (arg0) == NEGATE_EXPR
   10812		  && integer_onep (arg1)
-> 10813		  && !TYPE_OVERFLOW_TRAPS (type))
   10814		return fold_build1_loc (loc, BIT_NOT_EXPR, type,
   10815				    fold_convert_loc (loc, type,
   10816						      TREE_OPERAND (arg0, 0)));
(lldb) bt
* thread #1: tid = 0xdac306, 0x0000000100523c52 cc1`fold_binary_loc(loc=0, code=MINUS_EXPR, type=0x0000000000000000, op0=0x0000000142c09bd0, op1=0x0000000142c1b048) + 6402 at fold-const.c:10813, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x0)
  * frame #0: 0x0000000100523c52 cc1`fold_binary_loc(loc=0, code=MINUS_EXPR, type=0x0000000000000000, op0=0x0000000142c09bd0, op1=0x0000000142c1b048) + 6402 at fold-const.c:10813
    frame #1: 0x0000000100549c2b cc1`fold_build2_stat_loc(loc=0, code=MINUS_EXPR, type=0x0000000000000000, op0=0x0000000142c09bd0, op1=0x0000000142c1b048) + 27 at fold-const.c:14985
    frame #2: 0x00000001005ff9a1 cc1`gcc_expression_from_isl_expression + 417 at graphite-isl-ast-to-gimple.c:175
    frame #3: 0x00000001005ff800 cc1`gcc_expression_from_isl_expression + 928
    frame #4: 0x00000001005ff818 cc1`gcc_expression_from_isl_expression + 24 at graphite-isl-ast-to-gimple.c:164
    frame #5: 0x00000001005ff800 cc1`gcc_expression_from_isl_expression + 928
    frame #6: 0x00000001005ffd26 cc1`translate_isl_ast + 229 at graphite-isl-ast-to-gimple.c:501
    frame #7: 0x00000001005ffc41 cc1`translate_isl_ast + 17
    frame #8: 0x00000001005ffc30 cc1`translate_isl_ast(context_loop=0x0000000142c031a0, node=0x0000000141f1acd0, next_e=0x0000000142d36f50, ip=0x00007fff5fbfeff0) + 128
    frame #9: 0x000000010060047c cc1`graphite_regenerate_ast_isl(scop=<unavailable>) + 844 at graphite-isl-ast-to-gimple.c:699
    frame #10: 0x00000001005f8a28 cc1`graphite_transform_loops() + 2280 at graphite.c:304
    frame #11: 0x00000001005f8ab1 cc1`execute(this=<unavailable>, fun=<unavailable>) + 33 at graphite.c:333
    frame #12: 0x0000000100783097 cc1`execute_one_pass(pass=0x0000000141e10f40) + 407 at passes.c:2149
    frame #13: 0x000000010078368e cc1`execute_pass_list_1(pass=0x0000000141e10f40) + 30 at passes.c:2201
    frame #14: 0x00000001007836a0 cc1`execute_pass_list_1(pass=0x0000000141e10ee0) + 48 at passes.c:2202
    frame #15: 0x00000001007836a0 cc1`execute_pass_list_1(pass=0x0000000141e10ac0) + 48 at passes.c:2202
    frame #16: 0x00000001007836a0 cc1`execute_pass_list_1(pass=0x0000000141e0fa40) + 48 at passes.c:2202
    frame #17: 0x00000001007836e9 cc1`execute_pass_list(fn=0x0000000142d1c738, pass=0x0000000141e0f980) + 25 at passes.c:2212
    frame #18: 0x00000001003ee215 cc1`expand_function(node=0x0000000142d3b000) + 245 at cgraphunit.c:1786
    frame #19: 0x00000001003f0847 cc1`compile() + 230 at cgraphunit.c:1920
    frame #20: 0x00000001003f0761 cc1`compile() + 2209
    frame #21: 0x00000001003f1026 cc1`finalize_compilation_unit() + 102 at cgraphunit.c:2341
    frame #22: 0x0000000100020d55 cc1`c_write_global_declarations() + 613 at c-decl.c:10463
    frame #23: 0x000000010085cc97 cc1`compile_file + 167 at toplev.c:562
    frame #24: 0x000000010085f43f cc1`toplev_main(argc=7, argv=0x00007fff5fbff390) + 3327 at toplev.c:1946

TIA

Dominique

             reply	other threads:[~2014-07-12 10:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-12 10:13 Dominique Dhumieres [this message]
2014-07-13 10:34 ` Roman Gareev
2014-07-13 12:35   ` Dominique Dhumieres
2014-07-13 13:14   ` Dominique Dhumieres
2014-07-13 14:49   ` Tobias Grosser
2014-07-15 15:19     ` Roman Gareev
     [not found]       ` <53C54C7E.5050102@grosser.es>
     [not found]         ` <CAFiYyc1LoP1VDX57CmV_mdULBAObGzvmwtJ1zQxOA78HDbHSKA@mail.gmail.com>
     [not found]           ` <53C7DB6F.1050707@grosser.es>
2014-07-18 10:52             ` Roman Gareev
2014-07-18 11:28               ` Tobias Grosser
  -- strict thread matches above, loose matches on Subject: below --
2014-07-05  7:06 Roman Gareev
2014-07-07 11:11 ` Tobias Grosser
2014-07-08 12:47   ` Roman Gareev
2014-07-08 13:18     ` Tobias Grosser
2014-07-11  9:01       ` Roman Gareev
2014-07-11  9:18         ` Tobias Grosser
2014-07-11 11:11           ` Roman Gareev
2014-07-11 11:15             ` Tobias Grosser
2014-07-11 13:42               ` Roman Gareev
2014-07-11 13:44                 ` Tobias Grosser

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=20140712101339.BF8C3105@mailhost.lps.ens.fr \
    --to=dominiq@lps.ens.fr \
    --cc=gareevroman@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=tobias@grosser.es \
    /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).