public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "su at cs dot ucdavis.edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/97578] ice during IPA pass: inline Date: Sat, 31 Oct 2020 12:55:39 +0000 [thread overview] Message-ID: <bug-97578-4-OtAfAZ0wCH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97578-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97578 Zhendong Su <su at cs dot ucdavis.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |su at cs dot ucdavis.edu --- Comment #4 from Zhendong Su <su at cs dot ucdavis.edu> --- Another test for the same crash (at -Os and -O2 w/o -g, but not at -O3): [533] % gcctk -O2 -c small.c during IPA pass: inline small.c: In function ‘e’: small.c:10:3: internal compiler error: Segmentation fault 10 | b(d); | ^~~~ 0xcf71ef crash_signal ../../gcc-trunk/gcc/toplev.c:330 0x825aad function_summary<clone_info*>::get(cgraph_node*) ../../gcc-trunk/gcc/symbol-summary.h:212 0x825aad clone_info::get(cgraph_node*) ../../gcc-trunk/gcc/symtab-clones.h:70 0x825aad cgraph_edge::redirect_call_stmt_to_callee(cgraph_edge*) ../../gcc-trunk/gcc/cgraph.c:1495 0xd932bf redirect_all_calls(copy_body_data*, basic_block_def*) ../../gcc-trunk/gcc/tree-inline.c:2963 0xd9697e copy_cfg_body ../../gcc-trunk/gcc/tree-inline.c:3118 0xd9697e copy_body ../../gcc-trunk/gcc/tree-inline.c:3294 0xd99ec0 expand_call_inline ../../gcc-trunk/gcc/tree-inline.c:5084 0xd9beb9 gimple_expand_calls_inline ../../gcc-trunk/gcc/tree-inline.c:5274 0xd9beb9 optimize_inline_calls(tree_node*) ../../gcc-trunk/gcc/tree-inline.c:5447 0xa968fb inline_transform(cgraph_node*) ../../gcc-trunk/gcc/ipa-inline-transform.c:763 0xc00f79 execute_one_ipa_transform_pass ../../gcc-trunk/gcc/passes.c:2240 0xc00f79 execute_all_ipa_transforms(bool) ../../gcc-trunk/gcc/passes.c:2287 0x82dbf5 cgraph_node::expand() ../../gcc-trunk/gcc/cgraphunit.c:1822 0x82f596 expand_all_functions ../../gcc-trunk/gcc/cgraphunit.c:1997 0x82f596 symbol_table::compile() ../../gcc-trunk/gcc/cgraphunit.c:2361 0x832b6f symbol_table::compile() ../../gcc-trunk/gcc/cgraphunit.c:2545 0x832b6f symbol_table::finalize_compilation_unit() ../../gcc-trunk/gcc/cgraphunit.c:2542 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions. [534] % [534] % cat small.c int printf (const char *, ...); int a; static void b(int c) { if (c) printf("%d", a); } void e() { int d = 0; b(d); }
next prev parent reply other threads:[~2020-10-31 12:55 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-26 11:35 [Bug c/97578] New: " dcb314 at hotmail dot com 2020-10-26 11:46 ` [Bug c/97578] " marxin at gcc dot gnu.org 2020-10-26 12:21 ` dcb314 at hotmail dot com 2020-10-26 12:37 ` hubicka at gcc dot gnu.org 2020-10-31 12:55 ` su at cs dot ucdavis.edu [this message] 2020-11-01 14:48 ` Jan Hubicka 2020-11-01 14:48 ` hubicka at ucw dot cz 2020-11-02 16:26 ` jamborm at gcc dot gnu.org 2020-11-03 10:56 ` cvs-commit at gcc dot gnu.org 2020-11-03 11:19 ` hubicka at gcc dot gnu.org 2020-11-03 11:21 ` jakub at gcc dot gnu.org 2020-11-03 11:25 ` Jan Hubicka 2020-11-03 11:25 ` hubicka at ucw dot cz 2021-04-27 11:39 ` jakub at gcc dot gnu.org 2021-07-28 7:05 ` rguenth at gcc dot gnu.org 2022-04-13 15:07 ` [Bug c/97578] [11 Regression] " redi at gcc dot gnu.org 2022-04-13 15:09 ` jakub at gcc dot gnu.org 2022-04-13 16:23 ` dcb314 at hotmail dot com 2022-04-13 17:21 ` jamborm at gcc dot gnu.org 2022-04-21 7:48 ` rguenth at gcc dot gnu.org 2023-05-29 10:03 ` 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-97578-4-OtAfAZ0wCH@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).