inkwell VS pjproject

Secondly, I have learned about LLVM, and I have learned about the Inkwell library on Rust (It's a New Kind of Wrapper for Exposing LLVM (Safely)). Has anyone used this library before? Is this a good practice? Is it suitable for my compiler? Can I write some optimization passes of my own using this library?

I am trying to use the inkwell Rust crate for working with LLVM. In Cargo.toml, I have specified the LLVM version using features = ["llvm15-0"]

inkwell is a great llvm binding for rust and it has an implementation of kaleidoscope

I'm working on a compiler that uses the LLVM wrapper Inkwell for compilation. In order to compile something in inkwell, unless I'm missing something (which I very well might be), you need two structs:

Compiler backends (If building JIT/machine compiled langauges) 1. cranelift 2. inkwell - safe rust wrapper around llvm

Haha small world. I think we go to the same university and I took the same or similar course a few years ago. If somebody hasn't done the work for you, you may have to do some instrumentation yourself depending on what you want to track IMO https://github.com/TheDan64/inkwell is the best LLVM wrapper for Rustland (Python's llvmlite is a bit easier to use though)

I'm currently using the Inkwell bindings for Rust, which I've found actually pretty nice. In terms of generating LLVM IR, the C bindings (which is what Inkwell uses internally) can do anything you want them to (definitely not limited to trivial languages as someone else here said.) I'm even using the LLVM garbage collection infrastructure, with no problems (well, no problems in generating it; the LLVM GC infrastructure works pretty well but is sparsely documented, so actually writing a GC is fairly difficult, but it's doable). The C bindings are actually more stable than the C++ bindings (!), although not quite as stable as the textual IR format; but without the bindings you would have to write code to generate the IR yourself, the compiler would be slower as it must be emitted as text and then reparsed in a different process, and you would have less control over optimization.

safe llvm bindings https://github.com/TheDan64/inkwell

As we reviewed in this article LLVM IR has many use-cases and allows us to analyze and optimize source code through its passes. Knowing IR language itself will help us to write our passes and build projects around it for debugging, testing, optimizing. Currently, LLVM IR doesn't have Rust API. It's mainly used through the C++ library. However, some user-created repos are available on crates.io. There is a Rust binding to LLVM's C API - llvm-sys and two other, more Rusty APIs that are using LLVM: inkwell and llvm-ir. And finally, if you want to learn how to write a LLVM pass you should start here.

Hello, I'm in the process of developing a multiplayer FPS game and recently delved into ICE connectivity (STUN/TURN). Currently, my setup involves a custom matchmaking server in C++, with UDP port handling on the client side through UPnP or a fallback custom relay server. While the current approach works well, I'm exploring options to simplify the project by incorporating existing technologies. I've come across Libjuice and Libpjsip for NAT traversal. Libjuice offers a nice and simple API, but it supports only one person. Hence, I'm considering Libpjsip. I came across their ICE demo script at https://github.com/pjsip/pjproject/blob/master/pjsip-apps/src/samples/icedemo.c and I'm curious about its performance, particularly the pj_ice_strans_sendto2 function. I'm keen to understand how it compares to my current implementation with Berkeley Sockets and whether Libpjsip is a suitable choice for multiplayer P2P games. Any insights or assistance would be highly appreciated. Thanks!

Things improved a lot thanks to the adoption of the pjsip stack.

When I look at stuff like pjsip, I get the impression, it would be huge amount of work. Am I mistaken?

The first issue I'm facing is I can't find lib folder which is mentioned in Using pjproject libraries for your own application heading in the above-mentioned link. I download the source code from this link.

For client and server, I'm only really familiar with https://www.pjsip.org/. It also comes with a bunch of code for doing phone calls, which really most SIP Stacks were built around. But those parts can just not be used.

PJSIP (https://github.com/pjsip/pjproject) is used as SIP framework