public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "akrl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug jit/98615] New: libgccjit crash while freeing 'clone_info' in 'cgraph_c_finalize' Date: Sun, 10 Jan 2021 11:14:59 +0000 [thread overview] Message-ID: <bug-98615-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98615 Bug ID: 98615 Summary: libgccjit crash while freeing 'clone_info' in 'cgraph_c_finalize' Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: jit Assignee: dmalcolm at gcc dot gnu.org Reporter: akrl at gcc dot gnu.org Target Milestone: --- Created attachment 49928 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49928&action=edit reproducer ==== $ gcc libgccjit_repro.c -lgccjit $ ./a.out munmap_chunk(): invalid pointer Aborted (core dumped) ==== What is going on is that a static function (CAR) is inlined via virtual clone and its symbol released. Eventually 'cgraph_c_finalize' calls 'clone_info::release' and this is where (not sure why) we crash. I believe this bug was introduced by: ae7a23a3fab Move clone_info to summary The first revision where is possible to reproduce on was unbroken few commits later with: 895fdc1f4c9 ipa: Fix segmentation fault in function_summary<clone_info*>::get(cgraph_node*) I found this because it breaks Emacs bootstrap on libgccjit.
next reply other threads:[~2021-01-10 11:14 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-10 11:14 akrl at gcc dot gnu.org [this message] 2021-01-11 8:10 ` [Bug jit/98615] " marxin at gcc dot gnu.org 2021-01-11 12:49 ` marxin at gcc dot gnu.org 2021-01-11 12:58 ` marxin at gcc dot gnu.org 2021-01-11 13:30 ` Andrea Corallo 2021-01-11 13:30 ` andrea.corallo at arm dot com 2021-01-11 17:15 ` cvs-commit at gcc dot gnu.org 2021-01-11 17:15 ` marxin at gcc dot gnu.org 2021-01-11 19:36 ` Andrea Corallo 2021-01-11 19:37 ` andrea.corallo at arm dot com 2021-01-12 8:17 ` marxin at gcc dot gnu.org 2021-01-12 9:15 ` Andrea Corallo 2021-01-12 9:15 ` andrea.corallo at arm dot com 2021-01-12 10:49 ` marxin at gcc dot gnu.org 2021-04-21 18:09 ` cvs-commit 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-98615-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).