compile a 32-bit LSB executable on arm and Execution error-> panic: unaligned 64-bit atomic operation

[912929782]

What is the issue you are having?
panic: unaligned 64-bit atomic operation

goroutine 1 [running]:
runtime/internal/atomic.panicUnaligned()
        C:/GoSDK/src/runtime/internal/atomic/unaligned.go:8 +0x24
runtime/internal/atomic.Xadd64(0x13571684, 0x1)
        C:/GoSDK/src/runtime/internal/atomic/atomic_arm.s:258 +0x14
github.com/allegro/bigcache/v3.(*cacheShard).hit(0x13571600, 0x5819c5d75cbda787)
        C:/Users/Joker/go/pkg/mod/github.com/allegro/bigcache/[email protected]/shard.go:403 +0x34
github.com/allegro/bigcache/v3.(*cacheShard).get(0x13571600, {0x214747, 0x4}, 0x5819c5d75cbda787)
        C:/Users/Joker/go/pkg/mod/github.com/allegro/bigcache/[email protected]/shard.go:79 +0x3d0
github.com/allegro/bigcache/v3.(*BigCache).Get(0x2498980, {0x214747, 0x4})
        C:/Users/Joker/go/pkg/mod/github.com/allegro/bigcache/[email protected]/bigcache.go:136 +0x8c

[janisz]

On ARM, 386, and 32-bit MIPS, it is the caller's responsibility to arrange for 64-bit alignment of 64-bit words accessed atomically via the primitive atomic functions (types Int64 and Uint64 are automatically aligned). The first word in an allocated struct, array, or slice; in a global variable; or in a local variable (because the subject of all atomic operations will escape to the heap) can be relied upon to be 64-bit aligned.

https://pkg.go.dev/sync/atomic#pkg-notes

So maybe we should switch to atomic.Int64 from int64

[janisz]

I see 3 options:

• move stats to the top of struct

  bigcache/shard.go

  Line 32 in caa3415

  stats Stats

• use atomic.Int64
• instead of atomic use lock (that's already there)
  https://github.com/allegro/bigcache/blob/main/shard.go#L403-L406

@912929782 How to reproduce this issue? Does it happen with go test ./... we'll need to extend our CI with non x86 arch https://github.com/marketplace/actions/run-on-architecture

[912929782]

I expect this problem to occur on x86 systems as well

[912929782]

Forget to say, I am in the library: https://github.com/jpillora/overseer to use bigcache operation, result in this error. @janisz

[mgwoj]

What help is needed to fix this issue?

[janisz]

We need to reproduce it, best in CI. Maybe we can use qemu for that 🤔