LLVM Port to-do list

[felixangell]

We're porting Alloy to LLVM, here's the to-do list:

• Functions
  • Function prototypes
  • Function declarations
  • Function body
  • Function pointers
  • Function Return Types
• Statements
  • Leave Statements
  • Function Calls
• Expressions
  • Unary Expressions
  • Binary Expressions
  • Function Calls
• If Statements
• Type Inference
• Match Statements
• For Loops
  • Indexed
  • Infinite
  • Condition
• Implementations
• Modules & Visibility
• Structures
  • Default structure values
  • Static structure initialization
  • Packing and unpacking structures
• Enumeration
• Variables
  • Global Variables
  • Local Variables kind of done, needs some work
  • Mutable Variables
  • Pointers
• Default Structure Values
• Memory Allocation/Free
• File Inclusion (??)
• C Bindings
• Option Types
• Tuples
• Arrays
• Extern functions/variables/...

[MovingtoMars]

I added an llvm mode to test.py (119ae96)
Just run ./test.py --llvm

[MovingtoMars]

Can you push your fork? I'd like to work on it.

[raoulvdberge]

Nice work so far @MovingtoMars @felixangell 👍

[felixangell]

@MovingtoMars Sure thing

[ghost]

Gj m8s 👍

[MovingtoMars]

So do you think the C bindings are working out, or would it be beneficial to switch to C++?

[felixangell]

@MovingtoMars I think C bindings aren't too bad. I think I'd rather steer clear from C++ for now ^{because it's shit}. Rust uses the LLVM c bindings for their codegen, so I'm checking out their code every now and then as a reference. Though they seem to have written a layer of abstraction over the bindings so its compatible, and a little cleaner.