From: Jeffrey Walton <noloader@gmail.com>
To: 47429@debbugs.gnu.org
Subject: bug#47429: Re 47429:allocating JIT code buffer failed: Permission denied
Date: Fri, 26 Mar 2021 21:29:07 -0400 [thread overview]
Message-ID: <CAH8yC8kGzeu3cWDNR+2xYNovPB4D3iV3Z8AY9HwYHmKi1aRK5g@mail.gmail.com> (raw)
In-Reply-To: <CAH8yC8m8d5uVWOAFAPdr_v5KCg_o6xAhiU+T17Way3ZaDuetDw@mail.gmail.com>
This looks like the Apple article of interest:
https://developer.apple.com/documentation/apple-silicon/porting-just-in-time-compilers-to-apple-silicon.
According to the article, the page should be mapped with MAP_JIT.
Before instructions are written, pthread_jit_write_protect_np should
be called. After writing the jitted code, call
pthread_jit_write_protect_np again and call sys_icache_invalidate.
It looks like the OpenJDK folks are also experiencing similar issues.
Jeff
next prev parent reply other threads:[~2021-03-27 1:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 22:48 bug#47429: allocating JIT code buffer failed: Permission denied Jeffrey Walton
2021-03-26 23:27 ` bug#47429: Re 47429:allocating " Jeffrey Walton
2021-03-26 23:34 ` Jeffrey Walton
2021-03-27 1:29 ` Jeffrey Walton [this message]
2021-03-27 2:39 ` Jeffrey Walton
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAH8yC8kGzeu3cWDNR+2xYNovPB4D3iV3Z8AY9HwYHmKi1aRK5g@mail.gmail.com \
--to=noloader@gmail.com \
--cc=47429@debbugs.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: link
Be 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).