public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/105093] New: ICE in expand_expr_addr_expr_1, at expr.c:7607 since r6-3529-gf11a7b6d57f6fcba Date: Tue, 29 Mar 2022 08:02:29 +0000 [thread overview] Message-ID: <bug-105093-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105093 Bug ID: 105093 Summary: ICE in expand_expr_addr_expr_1, at expr.c:7607 since r6-3529-gf11a7b6d57f6fcba Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: marxin at gcc dot gnu.org CC: aoliva at gcc dot gnu.org, dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at gcc dot gnu.org Target Milestone: --- The following crashes: $ cat nrvo.cpp struct X { X(); ~X(); }; volatile X test21() { X x; return x; } $ g++ nrvo.cpp -c -O2 -fsanitize=undefined -c during RTL pass: expand nrvo.cpp: In function ‘volatile X test21()’: nrvo.cpp:5:12: internal compiler error: in expand_expr_addr_expr_1, at expr.cc:8435 5 | volatile X test21() { | ^~~~~~ 0x7ea241 expand_expr_addr_expr_1 /home/marxin/Programming/gcc/gcc/expr.cc:8435 0xe95b46 expand_expr_addr_expr /home/marxin/Programming/gcc/gcc/expr.cc:8548 0xe95b46 expand_expr_real_1(tree_node*, rtx_def*, machine_mode, expand_modifier, rtx_def**, bool) /home/marxin/Programming/gcc/gcc/expr.cc:11767 0xe927fc expand_expr /home/marxin/Programming/gcc/gcc/expr.h:301 0xe927fc expand_expr_real_2(separate_ops*, rtx_def*, machine_mode, expand_modifier) /home/marxin/Programming/gcc/gcc/expr.cc:9057 0xe96da6 expand_expr_real_1(tree_node*, rtx_def*, machine_mode, expand_modifier, rtx_def**, bool) /home/marxin/Programming/gcc/gcc/expr.cc:10504 0xe99414 expand_expr /home/marxin/Programming/gcc/gcc/expr.h:301 0xe99414 expand_operands(tree_node*, tree_node*, rtx_def*, rtx_def**, rtx_def**, expand_modifier) /home/marxin/Programming/gcc/gcc/expr.cc:8314 0xe8fb82 expand_expr_real_2(separate_ops*, rtx_def*, machine_mode, expand_modifier) /home/marxin/Programming/gcc/gcc/expr.cc:9281 0xe96da6 expand_expr_real_1(tree_node*, rtx_def*, machine_mode, expand_modifier, rtx_def**, bool) /home/marxin/Programming/gcc/gcc/expr.cc:10504 0xe99414 expand_expr /home/marxin/Programming/gcc/gcc/expr.h:301 0xe99414 expand_operands(tree_node*, tree_node*, rtx_def*, rtx_def**, rtx_def**, expand_modifier) /home/marxin/Programming/gcc/gcc/expr.cc:8314 0xe8f8b2 expand_expr_real_2(separate_ops*, rtx_def*, machine_mode, expand_modifier) /home/marxin/Programming/gcc/gcc/expr.cc:10295 0xd626c5 expand_gimple_stmt_1 /home/marxin/Programming/gcc/gcc/cfgexpand.cc:3972 0xd626c5 expand_gimple_stmt /home/marxin/Programming/gcc/gcc/cfgexpand.cc:4033 0xd684f4 expand_gimple_basic_block /home/marxin/Programming/gcc/gcc/cfgexpand.cc:6080 0xd6a6c7 execute /home/marxin/Programming/gcc/gcc/cfgexpand.cc:6806 Please submit a full bug report, with preprocessed source (by using -freport-bug). Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions.
next reply other threads:[~2022-03-29 8:02 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-29 8:02 marxin at gcc dot gnu.org [this message] 2022-03-29 8:02 ` [Bug sanitizer/105093] " marxin at gcc dot gnu.org 2022-03-29 10:29 ` rguenth at gcc dot gnu.org 2022-03-29 13:56 ` jakub at gcc dot gnu.org 2022-03-30 8:50 ` cvs-commit at gcc dot gnu.org 2022-03-30 8:53 ` cvs-commit at gcc dot gnu.org 2022-03-30 8:54 ` [Bug sanitizer/105093] [9/10 Regression] " jakub at gcc dot gnu.org 2022-05-10 8:25 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:26 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:36 ` jakub 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-105093-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).