public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "e9925248 at stud4 dot tuwien dot ac dot at" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/23408] [4.1 Regression] ICE in cgraph_decide_inlining_incrementally (using freed GC memory) Date: Tue, 16 Aug 2005 21:23:00 -0000 [thread overview] Message-ID: <20050816212022.31015.qmail@sourceware.org> (raw) In-Reply-To: <20050815213014.23408.e9925248@stud4.tuwien.ac.at> ------- Additional Comments From e9925248 at stud4 dot tuwien dot ac dot at 2005-08-16 21:20 ------- I think, I found the cause of this: cgraph_early_inlining holds a list of cgraph nodes in the array order. In this example, cgraph_decide_inlining_incrementally removes all references known by the garbage collector to a node contained in this array, which has not been processed. Then it calls the ggc_collect. With checking enabled, the freed memory is overwritten so that the following access cause a segementation fault. If the call to the garbage collector in cgraph_decide_inlining_incrementally is removed, the file compiles: Index: ipa-inline.c =================================================================== RCS file: /cvs/gcc/gcc/gcc/ipa-inline.c,v retrieving revision 2.15 diff -u -p -r2.15 ipa-inline.c --- ipa-inline.c 28 Jul 2005 21:45:25 -0000 2.15 +++ ipa-inline.c 16 Aug 2005 21:18:18 -0000 @@ -1073,7 +1073,6 @@ cgraph_decide_inlining_incrementally (st node->local.self_insns = node->global.insns; current_function_decl = NULL; pop_cfun (); - ggc_collect (); } return inlined; } -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23408
next prev parent reply other threads:[~2005-08-16 21:20 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-08-15 21:31 [Bug middle-end/23408] New: ICE on valid, if checking enabled e9925248 at stud4 dot tuwien dot ac dot at 2005-08-15 21:38 ` [Bug middle-end/23408] [4.1 Regression] ICE in cgraph_decide_inlining_incrementally (using freed GC memory) pinskia at gcc dot gnu dot org 2005-08-16 21:23 ` e9925248 at stud4 dot tuwien dot ac dot at [this message] 2005-08-16 21:24 ` Andrew Pinski 2005-08-16 21:30 ` pinskia at physics dot uc dot edu 2005-08-28 1:57 ` pinskia at gcc dot gnu dot org 2005-08-28 3:13 ` pinskia at gcc dot gnu dot org 2005-08-28 8:11 ` pinskia at gcc dot gnu dot org 2005-08-29 17:49 ` cvs-commit at gcc dot gnu dot org 2005-08-29 17:50 ` pinskia at gcc dot gnu dot 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=20050816212022.31015.qmail@sourceware.org \ --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).