tree 9b2a2d61ac7f82ec700676d60b61fdc49c7484d5
parent 7567fb385ba13871ceea19bb4d2c203bd0aafc75
author hlopko <hlopko@google.com> 1550913721 -0800
committer Copybara-Service <copybara-worker@google.com> 1550913833 -0800

Expose is_using_fission crosstool variable for compile actions

Before, per_object_debug_info_file was exposed for compilation actions, and is_using_fission for linking actions. It makes sense to have is_using_fission variable for both. I'm keeping per_object_debug_info variable there for actions that produce the .dwo file.

It's important to note that not all compile actions generate .dwo, even when using fission. In case of thin_lto, we only produce the file by the backend compile actions. But for bitcode compile action we still want to enable is_using_fission.

RELNOTES: is_using_fission crosstool variable is now exposed in all compile actions when fission is active (it used to be exposed only for linking actions).
PiperOrigin-RevId: 235321858