News for hackers. Stuff that matters.

A comment on Ampere switching to in-house CPU designs. Parent comment

Re:Ampere switching to in-house CPU designs by mumblemumble on Thursday May 20, 2021 @02:07PM (#27224813)
It at least gets you in the same ballpark. I'm not allowed to hook a debugger up to anything in the staging environment, and it's not terribly fun to be stuck, for example, having to guess at how memory fences are behaving in production because all the machines where you can test things empirically have a different memory model.

Or, for example, there's one library I use that includes some inline assembly language routines. Which target SSE, not SVE. So, if we're targeting different ISAs, then my dev box isn't even executing the same code as what would be running in production.

[ Parent | on HN ]
Re:Ampere switching to in-house CPU designs by Sindisil on Thursday May 20, 2021 @05:36PM (#27227636)
> I'm not allowed to hook a debugger up to anything in the staging environment

That seems crazy to me. What bizarre excuse does your organization have for that policy?

To me, part of the point of a staging environment is to provide something as close as practical to prod in which to test, reproduce, evaluate, and investigate issues, be they performance, correctness, or what have you.

[ Parent | on HN ]
Re:Ampere switching to in-house CPU designs by mumblemumble on Thursday May 20, 2021 @06:57PM (#27228483)
Honestly, does it even matter?

Even if it were allowed, it would still be awkward. I want to, as much as is practicable, find problems as early as possible, and not wait for them to get all the way to staging. I'm not really interested in making myself less able to do my job effectively just because I can.

[ Parent | on HN ]