4 ms·

It seems to still have trouble compiling code using old-style advices. By not supporting LLVM JIT, this also brings in a lot of extra dependencies on macOS, alt

It seems to still have trouble compiling code using old-style advices. By not supporting LLVM JIT, this also brings in a lot of extra dependencies on macOS, although, not as egregious as librsvg.

rurban 5y ago
By not supporting LLVM JIT it gains a lot of significant advantages: Small jit dependency. 1MB compared to 30MB. Fast JIT. At least 3x faster than llvm. All architectures. LLVM only supports a tiny amount of architectures, gccjit all. Only the desperate do llvm jitting.
- wyuenho 5y ago
  Besides ARM and AMD64, what other arch do you need to support? RISC-V? I'm using MacPorts and I have no idea how to hand compile just libgccjit there. The libgcc port doesn't even produce the jit language.
  - sanxiyn 5y ago
    That's a MacPorts problem. Debian has libgccjit0 package for example. In due time, MacPorts will also package gccjit.
  - rurban 5y ago
    Google helps: https://gist.github.com/AllenDang/f019593e65572a8e0aefc96058a2d23e https://gist.github.com/AllenDang/f019593e65572a8e0aefc96058... Macports has gccjit since gcc10, just somebody needs to update Emacs. What others archs? All of course
    - wyuenho 5y ago
      Google should also help you understand that the libgcc port does not provide for libgccjit for whatever reason. I'm writing my own Portfile to get libgccjit 11 now. The emacs-devel port does bring in the entire gcc10, but I just want libgccjit.
  - riffraff 5y ago
    I think you want to do port install emacs-devel +nativecomp or port install emacs-app-devel +nativecomp
    - jonnycomputer 5y ago
      I did this last night. It failed to compile. OSX 10.14. Frustratingly.
      - riffraff 5y ago
        I'm on macOS 11.2.3 (20D91) and it worked fine, though it took a while to compile since there were no binaries. You may try to report a bug[0] for Mojave but I wouldn't hold my breath. [0] https://trac.macports.org/wiki/MojaveProblems https://trac.macports.org/wiki/MojaveProblems

It seems to still have trouble compiling code using old-style advices. By not supporting LLVM JIT, this also brings in a lot of extra dependencies on macOS, although, not as egregious as librsvg.

rurban 5y ago

By not supporting LLVM JIT it gains a lot of significant advantages: Small jit dependency. 1MB compared to 30MB. Fast JIT. At least 3x faster than llvm. All architectures. LLVM only supports a tiny amount of architectures, gccjit all. Only the desperate do llvm jitting.

wyuenho 5y ago
Besides ARM and AMD64, what other arch do you need to support? RISC-V? I'm using MacPorts and I have no idea how to hand compile just libgccjit there. The libgcc port doesn't even produce the jit language.
- sanxiyn 5y ago
  That's a MacPorts problem. Debian has libgccjit0 package for example. In due time, MacPorts will also package gccjit.
- rurban 5y ago
  Google helps: https://gist.github.com/AllenDang/f019593e65572a8e0aefc96058a2d23e https://gist.github.com/AllenDang/f019593e65572a8e0aefc96058... Macports has gccjit since gcc10, just somebody needs to update Emacs. What others archs? All of course
  - wyuenho 5y ago
    Google should also help you understand that the libgcc port does not provide for libgccjit for whatever reason. I'm writing my own Portfile to get libgccjit 11 now. The emacs-devel port does bring in the entire gcc10, but I just want libgccjit.
- riffraff 5y ago
  I think you want to do port install emacs-devel +nativecomp or port install emacs-app-devel +nativecomp
  - jonnycomputer 5y ago
    I did this last night. It failed to compile. OSX 10.14. Frustratingly.
    - riffraff 5y ago
      I'm on macOS 11.2.3 (20D91) and it worked fine, though it took a while to compile since there were no binaries. You may try to report a bug[0] for Mojave but I wouldn't hold my breath. [0] https://trac.macports.org/wiki/MojaveProblems https://trac.macports.org/wiki/MojaveProblems