Stop printing a million instrumeting AArch64 loads/stores, as they're distracting

[kkysen]

No description provided.

[fw-immunant]

We should have some straightforward way to distinguish our modified compiler from the stock one. Maybe gate this the printing under an environment variable?

EDIT: I mean that it might be best to just make these prints opt-in.

[kkysen]

We should have some straightforward way to distinguish our modified compiler from the stock one. Maybe gate this under an environment variable?

What about just printing the message once the first time then?

[fw-immunant]

Also, the pattern we're following right now is basically to use branches as tags (which is admittedly ugly); currently CI on IA2 uses the fw/tweak-tagging branch, so future development should be atop that one. Additionally, IA2 CI currently caches clang based on the branch name, so updates to an existing branch won't be picked up until the cached CI artifacts are deleted. So we should either create a new branch or change IA2 CI to cache based on commit hash instead of branch name.

[fw-immunant]

We should have some straightforward way to distinguish our modified compiler from the stock one. Maybe gate this under an environment variable?

What about just printing the message once the first time then?

The advantage to printing for every function is that it's easy to see from logs if a given function was compiled with this compiler toolchain or not. That question is relevant in the presence of object files and static libs from the toolchain that also contribute code to the binaries we end up emitting.