What version of Go are you using (go version)?

go version go1.19.5 linux/amd64

Does this issue reproduce with the latest release?

Yes the issue can be reproduced with 1.19.5 as well as go1.18.1 where I first encountered it.

What operating system and processor architecture are you using (go env)?

My host system used for crosscompiling:

GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/sebastian/.cache/go-build"
GOENV="/home/sebastian/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/sebastian/go/pkg/mod"
GONOPROXY="gitlab.hpc.devnet.itwm.fhg.de"
GONOSUMDB="gitlab.hpc.devnet.itwm.fhg.de"
GOOS="linux"
GOPATH="/home/sebastian/go"
GOPRIVATE="gitlab.hpc.devnet.itwm.fhg.de"
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="off"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.19.5"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build3492048443=/tmp/go-build -gno-record-gcc-switches"

I currently don't have go installed on the Raspi, so no go env output there.
It's a Pi 3, so BCM2837 (armv7l) running a 32bit linux.

What did you do?

I cross compiled the program below using GOOS=linux GOARCH=arm GOARM=7 go build -o f32test main.go and ran it on a raspberry pi.

package main

import "fmt"

func main() {
	var f float32
	f = -1.0

	fmt.Printf("float32 to uint32: %v\n", uint32(f))
	fmt.Printf("float32 to uint64: %v\n", uint64(f))
	fmt.Printf("float32 to int32: %v\n", int32(f))
	fmt.Printf("float32 to int64: %v\n", int64(f))

	fmt.Printf("float32 to int32 to uint32: %v\n", uint32(int32(f)))
	fmt.Printf("float32 to int64 to uint64: %v\n", uint64(int64(f)))
}

What did you expect to see?

I expected to see an output consistent with the one on my amd64 system:

float32 to uint32: 4294967295
float32 to uint64: 18446744073709551615
float32 to int32: -1
float32 to int64: -1
float32 to int32 to uint32: 4294967295
float32 to int64 to uint64: 18446744073709551615

What did you see instead?

The output on the raspberry pi is:

float32 to uint32: 0
float32 to uint64: 18446744073709551615
float32 to int32: -1
float32 to int64: -1
float32 to int32 to uint32: 4294967295
float32 to int64 to uint64: 18446744073709551615

Comments

I did also check the language specs.
The section on numeric types in the language spec states, that float32 and int32, and uint32 are predeclared architecture-independent numeric types, so I’d expect their behavior to be the same across different architectures.
Also the section on conversions does not mention any undefined or architecture specific behaviour.

Let me know if you need any further information.