byuccl/coast

Compiler Assisted Software Fault Tolerance

coast's Issues

Was COAST tested with tail calls?

I'm seeing this output with LLVM-15, and for the moment it appears to be related to tail call instructions:

Attribute 'align' should have an Argument

I'm not currently in a position to test whether the LLVM-7 regression tests actually produced tail calls, so I figured I'd just ask before diving into this rabbit-hole.

CFCSS implementation not accurate?

Hi, thanks for open-sourcing this work. Been really helpful. I am currently working with CFCSS pass to harden my embedded firmware and I find the updates to global registers @BasicBlockSignatureTracker, @RunTimeSignatureAdjuster shouldn't be at the end of BB (i.e. in X.split) rather they should be just after their usage in XOR calculation near the start as mentioned in the CFCSS paper. This is important as current CFCSS suffers from poor CFE coverage. By manually modifying the generated cfcss code I was able to get better coverage.

I could patch it up but maybe you guys knowing the codebase could do it much quicker obviously after agreeing that CFCSS pass needs fixing

Possible Support for Windows?

Hey guys,

Thanks for making this public.

I would like to try this tool out on some MSP430 software that I've written in the CCS IDE. Would it be possible to get some guidance on how to operate COAST on a windows machine? I've been taking a crack at it, but I can't seem to get LLVM or the COAST passes to compile properly.

Any help would be greatly appreciated!

Support for later versions of LLVM?

Has anyone moved COAST to a later version of LLVM? Are there any plans to do so?

I'm open to helping, but I'm an LLVM newbie so there's only so much I can do. The code in cloning.cpp is giving me particular compile-time trouble.