David Nadlinger

@9il: What would probably be most useful is to generate the LLVM IR for the kernel function (`-output-ll`) and post it at bugs.llvm.org together with the assembler listings, possibly CCing...

Okay, thanks. If there are any issues with the account, I can also make the report for you.

Any update on this? And does LLVM 4.0 only decrease performance on your code or are there improvements as well? We'll have to decide on the compiler to use to...

@9il: See Gitter – you might need to turn off detection of LLD headers explicitly with LLVM 5.0 until this is fixed.

Just to throw it out there, regarding the "modulator" bullet point: Another use case that's quite important to us (i.e. already deployed) is to modulate the PI setpoint (i.e. input...

> but please decode the backtrace. Ah, the second chunk of lines in the above is already the decoded backtrace.

This turns out to be easy to reproduce, or at least an adjacent bug is: Just print a non-ASCII character from the kernel, e.g. ```python from artiq.experiment import * class...

(This lead to:) ``` panic at src/libcore/result.rs:945:5called `Result::unwrap()` on an `Err` value: Utf8Error { valid_up_to: 0, error_len: None } ```

The generated IR seems obviously wrong: ```llvm @S.nn = private unnamed_addr constant [3 x i8] c"n:n" @S.sn = private unnamed_addr constant [3 x i8] c"s:n" @S. = private unnamed_addr constant...

Ah, interesting; then just the length is wrong. Edit: Fixed the above; I had accidentally used upper-case sigma (U+03A3). If I read the IR correctly, it's still a byte short,...