public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "clyon at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/96136] New: [11 regression] ICE in reduce_to_bit_field_precision
Date: Thu, 09 Jul 2020 15:20:54 +0000 [thread overview]
Message-ID: <bug-96136-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96136
Bug ID: 96136
Summary: [11 regression] ICE in reduce_to_bit_field_precision
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: clyon at gcc dot gnu.org
Target Milestone: ---
Hi,
Since r11-1914-g760df6d296b8fc59796f42dca5eb14012fbfa28b, I've noticed an ICE
while building glibc-2.29 when GCC is configured --target
arm-none-linux-gnueabihf --with-cpu cortex-a15 --with-mode thumb --with-fpu
neon-vfpv4
$ arm-none-linux-gnueabihf-gcc -c -O2 iso646.i
during RTL pass: expand
In file included from iso646.c:901:
../iconv/skeleton.c: In function 'gconv':
../iconv/skeleton.c:390:1: internal compiler error: in
reduce_to_bit_field_precision, at expr.c:11530
390 | FUNCTION_NAME (struct __gconv_step *step, struct __gconv_step_data
*data,
| ^~~~~
0x92fdc3 reduce_to_bit_field_precision
/home/christophe.lyon/src/GCC/sources/gcc-fsf-git/trunk/gcc/expr.c:11530
0x9397b9 expand_expr_real_2(separate_ops*, rtx_def*, machine_mode,
expand_modifier)
/home/christophe.lyon/src/GCC/sources/gcc-fsf-git/trunk/gcc/expr.c:9276
0x9254c0 expand_expr_real_1(tree_node*, rtx_def*, machine_mode,
expand_modifier, rtx_def**, bool)
/home/christophe.lyon/src/GCC/sources/gcc-fsf-git/trunk/gcc/expr.c:10152
0x92fbbe expand_expr
/home/christophe.lyon/src/GCC/sources/gcc-fsf-git/trunk/gcc/expr.h:282
0x92fbbe expand_operands(tree_node*, tree_node*, rtx_def*, rtx_def**,
rtx_def**, expand_modifier)
/home/christophe.lyon/src/GCC/sources/gcc-fsf-git/trunk/gcc/expr.c:8065
0x939972 expand_cond_expr_using_cmove
/home/christophe.lyon/src/GCC/sources/gcc-fsf-git/trunk/gcc/expr.c:8519
0x939972 expand_expr_real_2(separate_ops*, rtx_def*, machine_mode,
expand_modifier)
/home/christophe.lyon/src/GCC/sources/gcc-fsf-git/trunk/gcc/expr.c:9869
0x7ead60 expand_gimple_stmt_1
/home/christophe.lyon/src/GCC/sources/gcc-fsf-git/trunk/gcc/cfgexpand.c:3787
0x7ead60 expand_gimple_stmt
/home/christophe.lyon/src/GCC/sources/gcc-fsf-git/trunk/gcc/cfgexpand.c:3847
0x7f20cb expand_gimple_basic_block
/home/christophe.lyon/src/GCC/sources/gcc-fsf-git/trunk/gcc/cfgexpand.c:5888
0x7f47bb execute
/home/christophe.lyon/src/GCC/sources/gcc-fsf-git/trunk/gcc/cfgexpand.c:6572
next reply other threads:[~2020-07-09 15:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 15:20 clyon at gcc dot gnu.org [this message]
2020-07-10 7:20 ` [Bug middle-end/96136] " rguenth at gcc dot gnu.org
2020-07-11 16:43 ` dcb314 at hotmail dot com
2020-07-12 8:05 ` clyon 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-96136-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).