Jorropo
Jorropo
> This doesn't seem to match the general model for `io.Pipe`, which is that reads and writes are matched when possible. I don't understand what this means. I shouldn't have...
I think I get it now, it's that one call to write will always match one call to read (assuming the read buffer is big enough). That seems to be...
@geraldss can you please show one program that has different behavior assuming we access the location of zero sized variables and assuming we do not ?
@geraldss I am not talking about what the current compiler is doing. I am asking let's say there are two hypothetical compilers, one that always load zero sized values when...
> const declarations are also in the spec and are defined to preclude superfluous lookups. Const declaration exists to support things `var`s do not: - immutable values - untyped values...
It's pretty minor, using `MOVQ` is just as fast, the register renaming unit can rename all three in one cycle even if there is a dependency. However because we encode...
This is ancient, modern releases of go can hash at ~2GiB/s per core on all modern amd64 cores (thx to new shani accelerated crypto), we also used a third party...
Actually the errors seen are different ? maybe different versions of glibc, reopen.
@jvoisin this is surprising indeed, I belive this script does little, I think we could port it to `sh` easily. Btw just like any go program you can do `go...
I would be surprising to have any user of the go target because it import private packages that are only found in the go compiler: > ```go > import "cmd/internal/obj"...