Nolan
Nolan
This comment is highly suggestive: https://github.com/emacs-mirror/emacs/blob/c67befd662571a822f3183c114ce3b1ad02e0ed9/lisp/term/xterm.el#L677
Awesome, thanks again for the debugging help and for making explain-pause-mode!
I ran into the same problem. The openssl asm puts constants (rodata, essentially) in the .text segment, which confuses BOLT. I worked around it by putting the constants into .rodata....
Actually, the "reference in the middle of instruction detected" warning is a new regression in BOLT since 71e5fc4a6734869bee50b6f2430c30d8a155e9d. I just tried with an up to date BOLT and am now...
Since I'm running BOLT on a shared library, this actually fails instead of just printing warnings: BOLT-WARNING: conditional tail call detected in function GFp_bn_power5/1 at 0xf129c. BOLT-WARNING: reference in the...
I have a patch that makes it work with 71e5fc4a6734869bee50b6f2430c30d8a155e9d BOLT. I'll ask about posting it, I am working on a contract at the moment.
I've attached the patches, sorry for the delay. Two caveats: 1. These are patches against "ring", which is a rust library than embeds parts of boringssl, which is a fork...
I plan to upstream them to ring, and will probably also submit them to boringssl and openssl. The global symbol thing is just a hack, but I didn't worry about...
The readme now claims PIE/.so support is in. I've not tried it yet, so I have no idea how well it works.
Tried it, seems to work on a mix of rust/C/C++/asm linked into a .so to run in an Intel SGX enclave. Even without -fno-jump-tables. It did print this: `BOLT-INFO: forcing...