PiperOrigin-RevId: 936808182
Change-Id: Iaef0f1c75d9df3fde061985b664d398f80231746

Verify that thin_lto feature is propagated correctly and generates expected actions (CppLTOIndexing, CcLtoBackendCompile).

PiperOrigin-RevId: 937170237
Change-Id: I8d579119e98f928fe6c9cebe761e6f2a7fb4bb27

Migrated tests:
- testActionGraph
- testLinkshared
- testNoLinkstatic
- testLtoBackendEnv
- testFission
- testNoLinkstaticFission
- testLinkstaticCcTestFission

PiperOrigin-RevId: 937187362
Change-Id: Ia2b3d17e59e00748f20ee1c9463ead0f9e465dfe

Migrated tests:
- testLinkstaticCcTest
- testTestOnlyTarget
- testUseSharedAllLinkstatic
- testAssemblerSource
- testNoSourceFiles
- testFdoInstrument

PiperOrigin-RevId: 937202153
Change-Id: I2d064af55e1caf52436a1f0bdf1717485b7b30e7

…l presubmit.

This ensures that Bazel does not attempt to locate Android SDK/NDK on the MacOS presubmit workers, avoiding potential build failures related to Android toolchain resolution.

PiperOrigin-RevId: 938486612
Change-Id: I01292d6ef96ef06a9d3ad28a534cc44fa4f7053a

PiperOrigin-RevId: 938501847
Change-Id: I000d59a66d81d4090cd1e1a40e3834113213f0de

The change extracts FDO and Memprof profile changelists to populate build variables and configures the toolchain to pass them as compilation flags when active. Verified end-to-end integration by running aquery on a mock cc_binary target.

PiperOrigin-RevId: 938512174
Change-Id: I97ad4d4759356a0882668e3a4ae660bbebc29e4b

Migrated tests:
- testForcePicBuildVariable
- testLibrariesToLinkAreExported
- testLibrarySearchDirectoriesAreExported
- testLinkSimpleLibName
- testLinkVersionedLibName
- testLinkUnusualLibName

PiperOrigin-RevId: 938659951
Change-Id: I221ab9d7127b71365f2eb59a94a2d572a5d1f55e

Migrated tests:
- testInterfaceLibraryBuildingVariablesWhenLegacyGenerationPossible
- testInterfaceLibraryBuildingVariablesWhenGenerationPossible
- testInterfaceLibraryBuildingVariablesWhenGenerationNotAllowed
- testNoIfsoBuildingWhenWhenThinLtoIndexing

PiperOrigin-RevId: 938670252
Change-Id: I2e08b542cd5db6003e5b3cf261192c31391459a8

PiperOrigin-RevId: 939884047
Change-Id: Idbb9df339324413ed711deae0880b6e104bb3330

Migrated tests:
- testLtoIndexOpt
- testLtoStandaloneCommandLines
- testCopt
- testPerFileCopt
- testLtoBackendOpt
- testPerFileLtoBackendOpt
- testLinkOpt

PiperOrigin-RevId: 939911684
Change-Id: Ic5c7919edf9b858f718bf8ed89313e9a2bf9714f

Copybara Import from #736

BEGIN_PUBLIC
Make default OSX toolchain respect the use_libtool flag (#736)

Closes #736
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=#736 from dzbarsky:zbarsky/libtool 465c64a
PiperOrigin-RevId: 940195996
Change-Id: Id0754fc7d9da5254bee7e535fd3d68d17d7bd171

…est_lto_standalone_command_lines`.

This had broken //tests/cc/common:test_lto_standalone_command_lines on  https://buildkite.com/bazel/rules-cc/builds/5560 for Bazel HEAD; it was caused by unknown commit

PiperOrigin-RevId: 940430076
Change-Id: I737ac11551677efe25b6bb55e269d0b1c2994d41

Copybara Import from #747

BEGIN_PUBLIC
Add Windows ThinLTO arguments (#747)

Windows rule-based toolchains currently reuse ELF LLD ThinLTO plugin options and `/dev/null`, which are not valid for LLD's COFF driver or Windows backend actions. This change selects the LLD COFF ThinLTO options, uses `/start-lib` and `/end-lib` for object-file groups, and uses `NUL` for indexless Windows backend actions.

This allows Windows toolchains that use LLD and provide `supports_start_end_lib` to enable rules_cc distributed ThinLTO.

Closes #747
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=#747 from dzbarsky:zbarsky/win-lto fad3b18
PiperOrigin-RevId: 940818026
Change-Id: I11c6542a1020983b20e3490af2b2e49b388105ac

…ain for adding runtimes-on-demand.

* Add `get_cc_runtimes` and `get_cc_runtimes_copts` implementations to `cc_helper[_internal]`.
* TODO update usage in `rules_python` and others to call `cc_helper` and deprecate `semantics.get_cc_runtimes*`

Basic Usage:

Define a provider like:
```
CcRuntimesInfo = provider(
    doc = "Information about runtime libraries to link into c++ targets.",
    fields = ["runtimes", "copts"],
)
```

Define a toolchain that returns that provider:
```
def _cc_runtimes_toolchain_impl(ctx):
    return [platform_common.ToolchainInfo(
        cc_runtimes_info = CcRuntimesInfo(
            runtimes = ctx.attr.runtimes,
            copts = ctx.attr.copts,
        ),
    )]
```
* `runtimes` is a collection of CcInfo providing targets
* `copts` provides compilation flags that must be used alongside this toolchain, e.g. to influence include ordering.

This may be used, e.g. in rules_android_ndk: bazelbuild/rules_android_ndk#93

PiperOrigin-RevId: 941244580
Change-Id: I31bade595714dbe44aa0d70afaa97ddd788e5635

…to linkstamp compile.

In https://github.com/rules_cc/bazel/commit/9cff17dd44cb500a06591355ce39bac66695aecf I added cpp build variables to with the expecation that I would use them in linkstamp compile but it turns out there is a direct approach which avoids this. So in this change, I've reverted the changes to compile_build_variables and introduced the necessary changes to cc_helper_internal.bzl.

PiperOrigin-RevId: 941422065
Change-Id: If1155391ad9fb3f180646cbb0ed18d387402c16a

PiperOrigin-RevId: 941497768
Change-Id: Idc08fbc4eb889964075bc0be921b5c9554c211ff

Copybara Import from #737

BEGIN_PUBLIC
Remove unused variable (#737)

Closes #737
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=#737 from keith:ks/remove-unused-variable 8a1c4b3
PiperOrigin-RevId: 941749895
Change-Id: Id94d46bdd2cb5f9baf2ce6cfa4bc548f83572381

Copybara Import from #761

BEGIN_PUBLIC
Starlarkify compute_output_name_prefix_dir (#761)

## Summary

Replace both `_cc_internal.compute_output_name_prefix_dir` calls with a private Starlark helper. The helper returns `non_arc` for purposes ending in `_non_objc_arc`, `arc` for purposes ending in `_objc_arc`, and an empty prefix otherwise.

`compile()` normalizes an unset purpose to an empty string before these calls, so the native helper's configuration-mnemonic fallback was not reachable from either rules_cc caller.

Configured-target coverage verifies that Objective-C ARC and non-ARC sources retain separate output directories.

Closes #761
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=#761 from dzbarsky:codex/starlarkify-compute-output-name-prefix-dir d06f9d3
PiperOrigin-RevId: 941761713
Change-Id: I3398d919cf7e4b287813de168b4b80f8373f0d6e

…on's parameters.

Java createCppCompileAction expects a boolean, this wasn't caught during testing until now.

https://storage.googleapis.com/bazel-untrusted-buildkite-artifacts/019f2441-e3e8-4e78-a3e0-aea267bfa919/src/test/shell/bazel/cc_integration_test/shard_7_of_10/test.log

PiperOrigin-RevId: 941839799
Change-Id: Ifaea4b3ac9cc70d81c503032f756ee460cfd1ded