In D53232#1216532, @jrtc27 wrote:

This will not fix that bug. fence is fence iorw, iorw, so all you are doing is relaxing some ordering requirements.

@jrtc27 I've update the revision, PTAL

In D53232#1216063, @jrtc27 wrote:

Do we actually have a proper definition of what *our* memory barrier APIs are meant to mean? What the ISA manual says is a sensible mapping isn't necessarily what we want; note that the table you're referencing is for "Linux memory primitives", and we are not Linux, nor do we follow its memory model.

@adamw Hi, is my patch OK or do I need more work on it?

In D50595#1155312, @adamw wrote:

In D50595#1155305, @mengzhuo1203_gmail.com wrote:

Thanks for review,
This change only affect download source code and binary for go itself.
The https://golang.org/dl/*.src.tar.gz redirect (HTTP 301) to go.dev/dl then Google blob file server.

Other golang.org namespace library (golang.org/x) won't change AFAIK.

I was unclear before: I'm saying that other ports need this change too. "golang.org" appears in some pkg-descr files, it appears in WWW in a number of ports, it appears in Mk/Uses/go.mk, etc.

Before approving and committing this patch, I wanted to encourage you to take a stab at extending this change for other ports too, if you're interested.

In D50595#1155303, @adamw wrote:

Good catch! I'm definitely in favor of switching, but:

1. 1. They'll need to leave the server up for basically ever because of all the programs and libraries depending on packages in the golang.org namespace
2. That URL has to be mentioned in more than just the lang/go* Makefiles. Have you checked for other Makefiles, pkg-descrs, pkg-message, pkg-message.in, etc? I fully agree about switching to go.dev, but it'd be a long-term win to switch the tree as a whole.