public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mrs at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/55610] cc1 is calling munmap() on part of itself on darwin Date: Thu, 06 Dec 2012 23:58:00 -0000 [thread overview] Message-ID: <bug-55610-4-AaODEhiRXC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55610-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55610 mrs@gcc.gnu.org <mrs at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mrs at gcc dot gnu.org --- Comment #3 from mrs at gcc dot gnu.org <mrs at gcc dot gnu.org> 2012-12-06 23:58:07 UTC --- We don't need to do that. We need to not run the unmap call in host-darwin.c when we dlopen things in the compiler; for example, dragonegg. Then, we need to test this and see if the bug is fixed. You can do that by adding in a #if 0 #end around the unmap call.
next prev parent reply other threads:[~2012-12-06 23:58 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-12-06 15:19 [Bug target/55610] New: " howarth at nitro dot med.uc.edu 2012-12-06 15:25 ` [Bug target/55610] " howarth at nitro dot med.uc.edu 2012-12-06 15:28 ` howarth at nitro dot med.uc.edu 2012-12-06 23:58 ` mrs at gcc dot gnu.org [this message] 2012-12-07 17:35 ` howarth at nitro dot med.uc.edu 2012-12-07 18:03 ` howarth at nitro dot med.uc.edu 2021-11-11 15:49 ` egallager at gcc dot gnu.org 2021-11-11 15:55 ` iains at gcc dot gnu.org 2021-12-02 19:45 ` cvs-commit at gcc dot gnu.org 2021-12-20 4:05 ` egallager at gcc dot gnu.org 2023-05-16 19:18 ` iains 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-55610-4-AaODEhiRXC@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).