core_log and rtio_log to ARTIQ
But only ARTIQ needs them in the forseeable future. nac3core is a compiler library, not a string formatter library. Keep it as simple as possible.
core_log and rtio_log to ARTIQ
with several arguments of the same type, as is required by the current implementation of varargs
So the _log functions currently have the same limitation, correct?
core_log and rtio_log to ARTIQ
So the present change should be reverted i.e. there is no need to add --target-features +sse2 ?
core_log and rtio_log to ARTIQ
Okay, but that comment is about Rust, not LLVM. nac3 is only using the latter here.
core_log and rtio_log to ARTIQ
Shouldn't this go into nac3artiq? I cannot think of a use for it in core.
core_log and rtio_log to ARTIQ
I suppose this should make it straightforward now to implement the full print_rpc() with several arguments?
core_log and rtio_log to ARTIQ
@abdul124 I thought you said this sse2 option was no longer required when using i686 instead of i386?
Works when NixOS does not crap out on nixos-rebuild switch. When it does, workaround is:
root@nixbld ~# ip route add 192.168.12.0/24 dev wlp6s0 table 1
root@nixbld ~# ip route add…Maybe just put a warning if the card next to it isn't short? Dynamic card size sounds difficult to implement and might make the design messy, doesn't sound worth it for this small problem.
This PR allows updating idle kernels by flashing -> running an experiment. The new idle kernel will start as expected on experiment finish.
That's not what I would expect. I would expect it…
That's just one of many issues with rust/cargo and trying to enforce the systematic use of --locked (or even --offline) is not really solving the problem.