Fabian Meumertzheim

Assuming that Gazelle compiles with any reasonably recent Go SDK, we could have the `go_sdk` extension provided by `rules_go` generate a repository that provides the label of the first host-compatible...

@ylecornec That looks pretty good. Could you split it into two parts, moving the addition of the new tag to the second one? The first one could be an easy...

@c-mita Not entirely sure whether it's relevant for this particular flag, but this may lack a line in `CoreOptions#getExec` to carry it over to the exec configuration.

@sgowroji This is a tracking issue for an incompatible flag, not stale.

@bazelbuild/triage Not stale @c-mita Do you have an update on the status and/or plans for this feature?

Maybe this could be done by having a well-known output group, similar to how validations use `_validation` and toggle whether it is requested via a flag? Then ruleset authors could...

I submitted https://github.com/bazelbuild/bazel/pull/21194, which adds `llvm-ifs` based support to the default Linux C++ toolchain. If you get a chance to try it out, let me know how it went. @MaskRay...

@kjteske Sounds great, please keep us updated about these efforts here. As the ARM case probably isn't relevant for the auto-configured toolchain shipped with Bazel, symbol versioning seems like the...

Can version information for *undefined* symbols affect the result of linking? If so, then skipping `.ifso` generation via `llvm-ifs` for shared objects with versioned symbols will disable this feature for...

> I can't think of a reason it would, but I am only 95% certain of this answer. Unfortunately it looks like this does indeed matter. The following Bazel integration...