public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fkastl at suse dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/112336] New: ICE in gen_reg_rtx emit-rtl.cc:1208 while compiling "unsigned _BitInt(1) Foo;" with -fsanitize=address Date: Wed, 01 Nov 2023 14:45:22 +0000 [thread overview] Message-ID: <bug-112336-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112336 Bug ID: 112336 Summary: ICE in gen_reg_rtx emit-rtl.cc:1208 while compiling "unsigned _BitInt(1) Foo;" with -fsanitize=address Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: fkastl at suse dot cz Target Milestone: --- Host: x86_64-linux Target: x86_64-linux Compiling a file with a single line (a reduced ext-int.c from llvm testsuite): --- ice.c --- unsigned _BitInt(1) GlobSize1; --- with -fsanitize=address: gcc -fsanitize=address ice.c results in an ICE: ice.c:1:1: internal compiler error: in gen_reg_rtx, at emit-rtl.cc:1208 1 | unsigned _BitInt(1) GlobSize1; | ^~~~~~~~ 0x77249b gen_reg_rtx(machine_mode) ../../src/gcc/emit-rtl.cc:1208 0xe94b89 maybe_legitimize_operand ../../src/gcc/optabs.cc:8044 0xe94b89 maybe_legitimize_operands(insn_code, unsigned int, unsigned int, expand_operand*) ../../src/gcc/optabs.cc:8199 0xe90ee9 maybe_gen_insn(insn_code, unsigned int, expand_operand*) ../../src/gcc/optabs.cc:8218 0xe99c0c expand_binop_directly ../../src/gcc/optabs.cc:1457 0xe97b29 expand_binop(machine_mode, optab_tag, rtx_def*, rtx_def*, rtx_def*, int, optab_methods) ../../src/gcc/optabs.cc:1544 0xbde1c0 expand_and(machine_mode, rtx_def*, rtx_def*, rtx_def*) ../../src/gcc/expmed.cc:5483 0xbf8544 expand_expr_real_1(tree_node*, rtx_def*, machine_mode, expand_modifier, rtx_def**, bool) ../../src/gcc/expr.cc:11005 0xc01fce expand_expr(tree_node*, rtx_def*, machine_mode, expand_modifier) ../../src/gcc/expr.h:310 0xc01fce expand_expr_addr_expr_1 ../../src/gcc/expr.cc:8728 0xc02639 expand_expr_addr_expr ../../src/gcc/expr.cc:8849 0xbf7894 expand_expr_real_1(tree_node*, rtx_def*, machine_mode, expand_modifier, rtx_def**, bool) ../../src/gcc/expr.cc:12163 0x1370de3 expand_expr(tree_node*, rtx_def*, machine_mode, expand_modifier) ../../src/gcc/expr.h:310 0x1370de3 output_constant ../../src/gcc/varasm.cc:5261 0x136fee8 output_constructor_regular_field ../../src/gcc/varasm.cc:5612 0x136fee8 output_constructor ../../src/gcc/varasm.cc:5878 0x136fee8 output_constructor_regular_field ../../src/gcc/varasm.cc:5612 0x136fee8 output_constructor ../../src/gcc/varasm.cc:5878 0x1371df5 assemble_variable_contents ../../src/gcc/varasm.cc:2231 0x1376f8d assemble_variable(tree_node*, int, int, int) ../../src/gcc/varasm.cc:2410
next reply other threads:[~2023-11-01 14:45 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-01 14:45 fkastl at suse dot cz [this message] 2023-11-01 15:31 ` [Bug sanitizer/112336] fsanitize=address vs _BitInt with a non-mode size (smaller than max mode size) pinskia at gcc dot gnu.org 2023-11-01 15:32 ` pinskia at gcc dot gnu.org 2023-11-22 16:40 ` jakub at gcc dot gnu.org 2023-11-22 18:18 ` [Bug middle-end/112336] " jakub at gcc dot gnu.org 2023-11-23 12:00 ` cvs-commit at gcc dot gnu.org 2023-11-23 12:01 ` jakub at gcc dot gnu.org 2023-11-24 7:16 ` pinskia at gcc dot gnu.org 2023-11-24 7:17 ` pinskia 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-112336-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: linkBe 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).