Marvin Drees

Thanks for giving it a try! > @MDr164 I've tried to look into this a couple of times since you created the PR. Perhaps I can outline my current understanding...

Really nice! It's fairly large so looking over everything might take time but so far this looks very promising. The gist is to strip out the image building and rely...

The target for me is the Aspeed AST2500 SoC which is `armv6k` but without FPU. Since Go 1.22 we actually got softfloat for ARM merged so I'm currently building with...

The PR i put up solves the initial issue I had for me at least as I don't have to target v5 anymore with my v6 and v7 softfloat targets....

Looks like CI is failing for code I didn't even touch in this PR. Otherwise this looks fine now. Will have to run a few more tests to be certain...

Actually I would need both ARMv6 and ARMv7 with softfloat support for my usecase and it's more about supporting the same naming scheme that upstream Go uses since 1.22. I...

Yep, that's also why this isn't anything high prio or blocking but might as well have it in to make use of the v7 features without an FPU. Still need...

That's why I wrote that I still need to figure out the flags :sweat_smile:. I left the identical for the draft just so I can post the general idea of...

> Just a quick reminder for this issue. > I have encountered the same practical problem as zygfryd and MDr164 regarding barcode & qr code scanners several times this year....

Hm, looks like adding the write permission to that one job borks the CI so that no other jobs run. Without that permission on the govulncheck job we can't post...