JalonSolov
JalonSolov
It was hand-written. Look in `vlib/v/gen/c/cheaders.v` starting on line 64, at the function `c_closure_helpers`. Looks like closures are currently supported on x86, x86_64, arm32, arm64, RISC-V 32, and RISC-V 64....
The only way to get this fixed on these extra architectures is for someone else to have access to systems with the same CPUs, or for you to provide login...
How can that even be tested without having access to the machine where it breaks? Either you'll have to create the fix, or someone who knows PowerPC well enough will...
For example, there have been over 1,600 commits since 0.3.4. Which one of those caused the problem?
Yes, qemu would be one way to get access to at least some of the arch's mentioned, but then which versions of which OSes? And that still doesn't address needing...
Try building with the following: ``` make v -prod self ``` instead of `make -f GNUmakefile` The `GNUmakefile` is mainly for *BSD systems, that need to use `gmake` instead of...
I pulled down a docker image of ubuntu 22.04, installed git and build-essential, then did the following ``` root@52856e212881:~# git clone https://github.com/vlang/v Cloning into 'v'... remote: Enumerating objects: 163543, done....
Also delete `~/.vmodules/cache` to make sure no cached values are interfering.
If you look at the `format_rfc3339` function, the first thing it calls is `local_to_utc`. That function looks like this: ```v // local_to_utc converts the receiver `t` to the corresponding UTC...