Stream: general

Topic: ✔ Help with cranelift array impl

Mensch272 (Aug 27 2022 at 10:12):

Hi all, I am trying to implement a brainfuck jit in cranelift. I cannot figure out how to implement the tape. I have basic compiler knowledge (implemented a few toy interpreted languages). This is my first time attempting jit. Any help is appreciated.

bjorn3 (Aug 27 2022 at 17:19):

Brainfuck clasically works with a 30_000 cell tape and 1 byte cells. As such you could allocate a 30_000 byte buffer and pass a pointer to this to the jitted code as argument. Next you can have the current tape location as argument and return value. Then you can then use iadd to add the buffer address and tape location to get the cell address and finally load.i8 and store.i8 to load and store the current cell.

bjorn3 (Aug 27 2022 at 17:20):

You will probably want to do bound checking to ensure that the brainfuck code doesn't go out out of the 30_000 cell bound.

Mensch272 (Aug 27 2022 at 18:21):

Would it be possible to allocate the buffer inside cranelift? I also want to compile it using cranelift-object.

Mensch272 (Aug 27 2022 at 18:32):

From what I can currently tell, I would have to use DataContent to declare data in the module. I'm not sure how i would use it afterward though.

bjorn3 (Aug 27 2022 at 21:12):

Yes, on unix you can call malloc and on windows I believe it is VirtualAlloc or something like that.

bjorn3 (Aug 27 2022 at 21:12):

For dynamic allocation that is.

bjorn3 (Aug 27 2022 at 21:14):

If you want a single static tape, you can use module.declare_data + module.define_data to define the tape and then module.declare_data_in_func followed by builder.ins().symbol_value(global) to get the address of the tape.

Mensch272 (Aug 28 2022 at 00:29):

Trying to load from the tape address gives an error.

let tape_addr = builder.ins().symbol_value(int, tape);

let load = builder.ins().load(
    types::I8,
    MemFlags::new(),
    tape_addr,
    Offset32::new(0),
);

Mensch272 (Aug 28 2022 at 00:30):

terminated by signal SIGSEGV (Address boundary error)

bjorn3 (Aug 28 2022 at 10:20):

How did you define the tape?

Mensch272 (Aug 29 2022 at 08:15):

let tape_id = {
    self.data_ctx.define_zeroinit(30_000);
    let id = self
        .module
        .declare_data("tape", Linkage::Local, true, false)
        .unwrap();
    self.module.define_data(id, &self.data_ctx).unwrap();
    self.data_ctx.clear();

    id
};

let tape = self.module.declare_data_in_func(tape_id, &mut builder.func);

bjorn3 (Aug 29 2022 at 11:31):

Did you call module.finalize_definitions() before calling the jitted function?

Mensch272 (Aug 30 2022 at 03:32):

aye

Mensch272 (Aug 30 2022 at 03:32):

let id = self
    .module
    .declare_function("main", Linkage::Export, &self.ctx.func.signature)
    .unwrap();

self.module.define_function(id, &mut self.ctx).unwrap();
self.module.clear_context(&mut self.ctx);
self.module.finalize_definitions();

let code = self.module.get_finalized_function(id);

bjorn3 (Aug 30 2022 at 07:55):

Weird. No idea what is going on. Sorry.

Afonso Bordado (Aug 30 2022 at 08:00):

Could it be is_pic on a Mac M1 (aarch64)? Do we have a specific error for that, or do we just crash?

@Mensch272 Is there a small sharable snippet that we could test locally?

Afonso Bordado (Aug 30 2022 at 08:02):

I think we crash with a descriptive message ("PLT is currently only supported on x86_64"), so its probably not that.

Mensch272 (Aug 30 2022 at 08:17):

I'm running fedora 36 with selinux-fix. I'll create a new project and share it here.

Afonso Bordado (Aug 30 2022 at 08:17):

Thanks! :heart:

Mensch272 (Aug 30 2022 at 16:29):

I created a new rust project using cargo, and copied the code from my previous project. The new project builds and runs correctly. The old project still throws the same error even after running cargo clean. Suffice it to say I am extremely confused. I will try to see if I can replicate the error.

Notification Bot (Aug 31 2022 at 11:07):

Mensch272 has marked this topic as resolved.

Last updated: Dec 23 2024 at 12:05 UTC