dataking

Expected to see Rust's approach mentioned since it occupies an interesting point in the design space, i.e., automatic memory management where lifetimes are (mostly) determined at compile-time vs. at run-time (RC and/or GC).

Not really. It controls continuous integration builds (or Pipelines in Microsoft parlance) on Azure DevOps. You can test on Linux, macOS, and Windows hosts.

> We've got to get more code out of C and into something with subscript checking. None of the kludges for fixing C work.

shameless plug: https://www.c2rust.com

> I wonder if one could do things like compile with rustc and clang and somehow compare the LLVM IR for equivalence

The approach we've taken so far with C2Rust is to build compiler plugins that instrument C and Rust code so we can dynamically check their behavior when fed the same input.

https://github.com/immunant/c2rust/tree/master/cross-checks

(I'm one of the contributors to c2rust.)

As harpocrates mentioned, we've been taken by surprise at the interest in the c2rust project. We've updated the website to acknowledge the inspiration we drew from Jamey's Corrode translator. Our apologies for not including the acknowledgments from day one!

I want to take the chance to mention that c2rust goes beyond transpiling C to (unsafe) Rust. We anticipate that even in the limit, the automatically translated code will need human-in-the-loop refactoring to arrive at idiomatic Rust. Therefore, we provide compiler plugins that instrument the original C code, the new Rust code to check whether the two programs behave identically when fed the same inputs. The checking can either happen at runtime (using a multi-variant execution environment to run the processes side by side) or offline based on logging. We'd love to hear what everyone thinks of this aspect too.

Thanks so much for letting me know; should be fixed now.

Edit: reflect resolved status of issue.

Really cool to see companies willing to migrate to a more modern language. I'm part of a team working on C to Rust migration tools (partly inspired by the Corrode translator).

Shameless plug/pre-alpha demo: https://www.c2rust.com

Edit: missing word.

Is your product DCAA compliant? As a small government contractor, my employer is required to use a DCAA compliant time tracking system. Anything that is not, is a non-starter. Please consider making the answer to compliance questions easy to find, even if you have to answer in the negative initially.

Immunant | Irvine, CA | ONSITE | REMOTE (US-only) | www.immunant.com/page/jobs

Immunant is building systems security tools that prevent vulnerability exploits.

We are looking to fill the following full-time roles:

1) Compiler, linker, and loader expert. Deep knowledge of C/C++, and ELF as well as x86, and ARM/AArch64 machine code expected. Previous experience with compiler and linker development preferred.

2) Rust aficionado for language migration project. Familiarity with all things Rust expected. Maybe you've contributed to Rust already? Experience with language parsing, refactoring, analysis, and/or rewriting preferred.

Apply here: www.immunant.com/page/jobs

Immunant | Irvine, CA | ONSITE | REMOTE (US-only) | www.immunant.com/page/jobs

Immunant is building systems security tools that prevent vulnerability exploits.

We are looking to fill the following full-time roles:

1) Compiler, linker, and loader expert. Deep knowledge of C/C++, and ELF as well as x86, and ARM/AArch64 machine code expected. Previous experience with compiler and linker development preferred.

2) Rust aficionado for language migration project. Familiarity with all things Rust expected. Maybe you've contributed to Rust already? Experience with language parsing, refactoring, analysis, and/or rewriting preferred.

Immunant | Irvine, CA | ONSITE | REMOTE (US-only) | www.immunant.com/page/jobs

Immunant is building systems security tools that prevent vulnerability exploits.

We are looking to fill the following full-time roles:

1) Compiler, linker, and loader expert. Deep knowledge of C/C++, and ELF as well as x86, and ARM/AArch64 machine code expected. Previous experience with compiler and linker development preferred.

2) Rust aficionado for language migration project. Familiarity with all things Rust expected. Maybe you've contributed to Rust already? Experience with language parsing, refactoring, analysis, and/or rewriting preferred.

Apply here: www.immunant.com/page/jobs

Immunant | Irvine, CA | ONSITE | REMOTE (US-only) | www.immunant.com/page/jobs

Immunant is building low-level security tools that prevent remote code execution.

We are looking to fill the following full-time roles:

1) Compiler, linker, and loader expert. Deep knowledge of C/C++, and ELF as well as x86, and ARM/AArch64 machine code expected. Previous experience with compiler and linker development preferred.

2) Rust afficionado for language migration project. Familiarity with all things Rust expected. Maybe you've contributed to Rust already? Experience with language parsing, refactoring, analysis, and/or rewriting preferred.

We're accepting interns too! Apply here: www.immunant.com/page/jobs

Immunant, Inc. | Information Security Researchers, Systems Programmers | Irvine, CA | ONSITE INTERNS VISA

Immunant is developing better exploit mitigations. We are looking for an additional team member who is as excited about systems programming, compiler construction, information security research as we are.

More info at http://immunant.com/page/jobs/

selfrando contributor here. it is correct that selfrando is intended as an improvement over ASLR by randomizing code at the function level (vs. module level). this improves resilience to information leaks somewhat, but with mitigations like these, there are no silver bullets.

selfrando github repo: https://github.com/immunant/selfrando feel free to open an issue or write us at team@immunant.com

cheers!

The steering-wheel to be precise :)

Very cool! I wish it would come with an API to integrate into text editors (Sublime Text, Emacs, Vim, etc.)

Shameless plug: Some time ago I authored a Sublime Text (2/3) plug-in that highlights use of passive voice and "weazel words" (i.e., words to use sparingly and words). To install from Package Control, just search for "Writing Style" :)