gccrs
libsignal
Our great sponsors
gccrs | libsignal | |
---|---|---|
102 | 24 | |
2,255 | 2,892 | |
1.6% | 4.4% | |
10.0 | 9.7 | |
3 days ago | 5 days ago | |
Rust | ||
GNU General Public License v3.0 only | GNU Affero General Public License v3.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
gccrs
-
FreeBSD evaluating Rust's adoption into base system
There is a Rust front-end for GCC that is under active development [1]. If the chip vendors are not willing to develop and upstream a LLVM back-end then they can feel free to start contributing to it.
[1] https://rust-gcc.github.io/
-
Why do lifetimes need to be leaky?
That's why gccrs doesn't even consider lifetime checking a part of the language (they plan to use Polonius, too).
- Rust-GCC: GCC Front-End for Rust
-
How hard would it be to port the Rust toolchain to a new non-POSIX OS written in Rust and get it to host its own development? What would that process entail?
There's ongoing work on a Rust front-end for GCC (https://github.com/Rust-GCC/gccrs). Bit barebones right now -- ie, even core doesn't compile -- but there's funding, demand, and regular progress, so it'll only get better from there. Once gccrs can compile core, it should be ready to compile most of Rust, and thus if you've taught the calling conventions for C to GCC, you're golden.
-
How hard is it to write a front end for a more complex language like Rust or Kotlin?
I recommend checking out the GCC Rust frontend project.
-
Rust contributions for Linux 6.4 are finally merged upstream!
That is what theyre refering to, yes. The GitHub is named https://github.com/Rust-GCC/gccrs
-
GCC 13 and the State of Gccrs
- But this misses so much extra context information
3. Macro invocations there are really subtle rules on how you treat macro invocations such as this which is not documented at all https://github.com/Rust-GCC/gccrs/blob/master/gcc/rust/expan...
Some day I personally want to write a blog post about how complicated and under spec'd Rust is, then write one about the stuff i do like it such as iterators being part of libcore so i don't need reactive extensions.
- Break rust Easter Egg Merged Into gccrs
-
Any alternate Rust compilers?
(Speaking of which, Rust-GCC (or gcc-rs or gccrs or whichever other of their names they decide is the primary one) isn't even going to be a complete C++ implementation. Their plan is to implement enough to compile Polonius (the NLL 2.0 borrow checker being developed in Rust for rustc) and then share that since borrow-checking isn't necessary for codegen... only to identify and reject invalid programs... making the C++ portion of it not that different in scope from mrustc.)
-
Which programming languages, if all legacy code written in them was ported to a more modern language, would become extinct?
That bridge will be crossed with gccrs (compiling Rust with gcc directly, coming next month with GCC 13) and rust_codegen_gcc (rustc frontend, GCC backend, works now but just doesn’t yet have an “easy” setup)
libsignal
- Police used Cellebrite to break into my phone, how do I prevent this in the future?
- EU haluaa kieltää vahvan salauksen - vaatii takaportteja viestisovelluksiin
- Signal has begun it's transition towards post-quantum key exchanges
-
libsignal-go built for go1.20+
I am in the process of building a Go implementation of the libsignal-protocol, which powers the Signal app.
-
End-to-end encrypted messages need more than libsignal
How is twitter intending to use libsignal? I doubt it would be via the primary AGPL license[1], forcing them to publish the source code of their server source code. Does signal sell private licenses?
[1] https://github.com/signalapp/libsignal/blob/main/LICENSE
-
Twitter Will Adopt Signal Protocol for Encrypted DMs
The Signal Protocol is licensed under AGPLv3 (see here).
Signal protocol is AGPL3 https://github.com/signalapp/libsignal
- Twitter to Encrypt Direct Messages Using Signal Protocol, Shows Code
- Elon Musk says he wants 'Twitter 2.0' to have video chat, voice calls, and encrypted DMs — and has enlisted the help of Signal's founder
-
Snap Store administrators removed signal-desktop from Ubuntu Snap
This is the license for libsignal: https://github.com/signalapp/libsignal/blob/main/LICENSE
The only reference to trademark is:
> Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms:
What are some alternatives?
gcc-rust - a (WIP) Rust frontend for gcc / a gcc backend for rustc
signal-cli - signal-cli provides an unofficial commandline, JSON-RPC and dbus interface for the Signal messenger.
rustc_codegen_gcc - libgccjit AOT codegen for rustc
axolotl - A Signal compatible cross plattform client written in Go, Rust and Vuejs
rustc_codegen_gcc - libgccjit AOT codegen for rustc
Signal-Desktop - A private messenger for Windows, macOS, and Linux.
mold - Mold: A Modern Linker 🦠
status-mobile - a free (libre) open source, mobile OS for Ethereum
rust - Empowering everyone to build reliable and efficient software.
openpgpjs - OpenPGP implementation for JavaScript
Rust-for-Linux - Adding support for the Rust language to the Linux kernel.
nimbus-eth2 - Nim implementation of the Ethereum Beacon Chain