public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/64108] ICE: SIGSEGV in decide_alg() with -mmemset-strategy=libcall:-1:align -minline-all-stringops
Date: Thu, 04 Dec 2014 05:13:00 -0000 [thread overview]
Message-ID: <bug-64108-4-sirIie9PxD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64108-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64108
--- Comment #3 from Zdenek Sojka <zsojka at seznam dot cz> ---
Created attachment 34187
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34187&action=edit
another autoreduced testcase (from gcc.c-torture/execute/20020412-1.c)
Hello, I am getting another similiar ICE (-minline-stringops-dynamically is
used it this case, different testcase):
$ gcc -mmemcpy-strategy=libcall:-1:align -minline-stringops-dynamically final.i
final.i: In function 'foo':
final.i:10:5: internal compiler error: in decide_alg, at
config/i386/i386.c:24506
d =
^
0xf0f862 decide_alg
/mnt/svn/gcc-trunk/gcc/config/i386/i386.c:24506
0xf5848f ix86_expand_set_or_movmem(rtx_def*, rtx_def*, rtx_def*, rtx_def*,
rtx_def*, rtx_def*, rtx_def*, rtx_def*, rtx_def*, rtx_def*, bool)
/mnt/svn/gcc-trunk/gcc/config/i386/i386.c:24759
0x106b68e gen_movmemdi(rtx_def*, rtx_def*, rtx_def*, rtx_def*, rtx_def*,
rtx_def*, rtx_def*, rtx_def*, rtx_def*)
/mnt/svn/gcc-trunk/gcc/config/i386/i386.md:15893
0xb18792 insn_gen_fn::operator()(rtx_def*, rtx_def*, rtx_def*, rtx_def*,
rtx_def*, rtx_def*, rtx_def*, rtx_def*, rtx_def*) const
/mnt/svn/gcc-trunk/gcc/recog.h:310
0xb18792 maybe_gen_insn(insn_code, unsigned int, expand_operand*)
/mnt/svn/gcc-trunk/gcc/optabs.c:8395
0xb18da8 maybe_expand_insn(insn_code, unsigned int, expand_operand*)
/mnt/svn/gcc-trunk/gcc/optabs.c:8407
0x8d8a3e emit_block_move_via_movmem
/mnt/svn/gcc-trunk/gcc/expr.c:1330
0x8d8a3e emit_block_move_hints(rtx_def*, rtx_def*, rtx_def*, block_op_methods,
unsigned int, long, unsigned long, unsigned long, unsigned long)
/mnt/svn/gcc-trunk/gcc/expr.c:1148
0x797721 expand_builtin_memcpy_args
/mnt/svn/gcc-trunk/gcc/builtins.c:3243
0x7a746c expand_builtin(tree_node*, rtx_def*, rtx_def*, machine_mode, int)
/mnt/svn/gcc-trunk/gcc/builtins.c:6288
0x8d45b6 expand_expr_real_1(tree_node*, rtx_def*, machine_mode,
expand_modifier, rtx_def**, bool)
/mnt/svn/gcc-trunk/gcc/expr.c:10471
0x7cb4c9 expand_expr
/mnt/svn/gcc-trunk/gcc/expr.h:299
0x7cb4c9 expand_call_stmt
/mnt/svn/gcc-trunk/gcc/cfgexpand.c:2347
0x7cbbff expand_gimple_stmt_1
/mnt/svn/gcc-trunk/gcc/cfgexpand.c:3293
0x7cbbff expand_gimple_stmt
/mnt/svn/gcc-trunk/gcc/cfgexpand.c:3447
0x7d1193 expand_gimple_basic_block
/mnt/svn/gcc-trunk/gcc/cfgexpand.c:5280
0x7d3686 execute
/mnt/svn/gcc-trunk/gcc/cfgexpand.c:5889
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.
next prev parent reply other threads:[~2014-12-04 5:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 21:16 [Bug target/64108] New: " zsojka at seznam dot cz
2014-11-29 14:07 ` [Bug target/64108] " hjl.tools at gmail dot com
2014-12-02 14:11 ` hjl at gcc dot gnu.org
2014-12-04 5:13 ` zsojka at seznam dot cz [this message]
2014-12-05 11:53 ` hjl at gcc dot gnu.org
2014-12-05 12:05 ` hjl.tools at gmail dot com
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-64108-4-sirIie9PxD@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).